Bi-directional property mappings used in combination with the 'Create' file property option currently wipes out existing Vault user property values on state transitions if the file doesn't yet have the file property created. It seems as though a state change does a mini property update with the file version that was created from the state transition based on property mapping choices. For bi-directional property mappings, it will update the Vault property value to match the file property value. If the property that has bi-directional mapping doesn't yet exist in the file, a "blank" value is written over to the Vault property. I would like to see this updated to either allow a mapping direction priority during these state changes or make it so that if the file doesn't yet have that property, it's not writing back a "blank" property value. My current situation is that we have a user defined property mapped bi-directionally with a custom iProperty in Inventor. Previously this custom iProperty was only needed in IDW file types. The custom iProperty is part of our IDW template, so we never needed to use the 'Create' option. We simply had it set up as bidirectional mapping. Now, I'd like to create the custom iProperty ipt and iam file types. The user property already exists as a Vault property for these files, so when I set the property up to 'Create', I expected the Vault property would be written to the file. Unfortunately, unless the user performs a property sync before they make a state transition, the Vault value for that property is wiped out if the file doesn't yet have the custom iProperty.
Show More