Synchronize Properties problem with Model States

[wwitt]

For files that use model states, each iProperty that is mapped to a Vault property gets overwritten to match the primary model state value when synchronizing properties using the job processor. 

Example screenshot with model state iProperties shown for each file version (part number changes):

This problem was originally found with our custom job processor add-in that has it's own sync properties code that was taken from a Vault customization blog that no longer exists (see attached file), but it has been reproduced with the built in Sync Properties job.

[Nick_Hall]

Hi

I'm not really sure what you are asking here, so I'll suggest a few things.

• Is there a way to configure the standard SyncProperties Job so it doesn't do this?
  I've not seen anything to say there is
  
  
• Can I modify my custom job so it doesn't do this?
  Almost certainly, but it's not going to be easy
  You will need to work out which properties you are happy to be updated as it does now, which ones you want to be updated from the active model state, and which ones you want to leave alone
  Then you'll have to use the Inventor API to determine whether the model has model states, and if so, retrieve the values you want and update the properties as you decide above.
  If it does not have model states, you can use the standard method.
  
  
• Can Autodesk fix this so that the standard job can work as you would like it to
  Post an idea in the Ideas forum, and if enough people like it, it might make it into the product
  I'd upvote it if you do

Hope some of that helps

Nick

[TylerWarner33]

Adding links to related resources for future reference:

• Syncing Vault Properties for Property Equivalence (C#) by Autodesk: Blog, Resources
• Synchronize File Properties (C#)  by CoolOrange