SetUserText and GetUserText would be what I’m actually after - so attributes could be specified per part, not per document.
Re: value tables, an ideal solution would be to reference an external .xls so we could update values once and they’d become options in the dropdown menus for all users dynamically.
Math functions aren’t that important.
Our primary goal is to have a PLM software have visibility to DocumentText and/or UserText so we can quickly pull up all files with ______ material, etc. We are trying to find the least painful way creating those attribute associations without having to SetUserText from scratch from the Command line. This new V6 functionality seems like a step in that direction.