AnsweredAssumed Answered

Configuration-Specific Custom Properties in the Vault

Question asked by Brad Hakeman on May 29, 2014
Latest reply on May 29, 2014 by Kenneth Barrentine

We were looking at using configurations since a lot of our assemblies vary slightly.


Using the Property Tab Builder, we made our Custom Properties "Show on Configuration Tab", so we could create configuration-specific custom properties. 


The problem now is when files are loaded into the vault, the Default Configuration Mapped Properties aren't filling in at check-in.


I guess my questions are:

  1. Are we using Configuration Specific custom properties correctly?  I had found a Macro that would copy the custom property fields into the configuration-specific properties, but this would be time consuming for some fastener models (trying to stay away from Toolbox at the moment)
  2. Should we stay away from configurations in WPDM entirely?
  3. If keeping configurations in the vault, how do you map the properties so they will auto-fill?
  4. How do you manage revisions in case one configuration is at a different revision? (never know, it could happen)