This content has been marked as final. Show 4 replies
cool catch, that could be very useful.
If there were a list, they would no longer be undocumented... no? >
1.) Because the data are SW System Values and they are not approved/documented, this may be why they are spitting out the "PRP:"
1.a.) You may be able to take advantage of the "Concatenate" & "MID" functions from Excel to parse the information. Not to sure about this working in SW BOMs though.
2.) I do not have an andswer to this but I sure could use this capability.
3.)The SW System Values that will probably work are just those that are identified in the File Properties dialog:
I would concur with Eddie on this one. There are a lot of things that you can sort of do, just because of some lucky tweak of the way SW was coded. However, using "undocumented" stuff like that is a bit risky because (even more than the documented stuff) it may or may not work later, and you certainly won't get any support at all if it doesn't work.
Also, the reason you gave for wanting to use this stuff (custom properties may not be set up for some files) is actually pretty risky. There are plenty of reasons for custom properties to not be populated. Are you going to trust info in the BOM that was just some default value? For example, say the template someone used to create a part has some default density like 1g/cc. Your "automatic" SW-Mass is going to be off.