...to understand if this is safe practice or just luck
In my Vault I have user defined properties like EAN, SAP number etc. They are mapped to iProperties of (Inventor) parts and assemblies. They are just metadata, nothing to do with the model geometry.
Sometimes I deal with situation where I need to assign or change values of these for released files. To avoid the need to do it via work-in-progress and re-release I either do it as admin or via quick-change. I do it in Vault, then these are automatically synced into the files.
What I was afraid of was that if I update a part like that, and the part is used in some assemblies that are released, it would cause Inventor to figure out these assemblies need to be updated as well, because their subcomponents got updated. In theory it should happen.
But in practice I don't see such behavior. If I open the assembly in Inventor, it won't tell that it noticed any change in its subcomponent. However if I check the subcomponent's iProperties - I do see my change.
I'm puzzled, yet very glad it doesn't cause the problem I expected. Could anyone help me understand what's going on?
