We have setup all our models to use configuration specific properties not custom properties so how do you map to this in the vaultadmin?
Kurt Schreib
We have setup all our models to use configuration specific properties not custom properties so how do you map to this in the vaultadmin?
Kurt Schreib
I am having this problem in Enterprise PDM as well.
My company makes use of configurations to deal with color finishes (see a sample configuration tree below). Even though we are only changing the material with our configurations, it's still important for us to be able to document our different part numbers of the different colored stock material. Using configurations is a heck of a lot more efficient than going through the trouble of creating and maintaining several different independent models with no differing geometry, just a few different properties and a different material.
The ability to map variables at the configuration level would go a long way towards helping to make our data cards more accurate and therefore more usable. Although I haven't discovered the technique yet, I'm sure that there's a way for me to map Custom properties directly to the configuration tabs. But it would be a whole lot nicer if I could just map the configuration specific properties directly.
not possible, hence the mapping refers only to "custom" properties.
the bigger dilemma is managing the configurations.
when a part is revised (revision increment) do all the configurations roll as well?
pdmw cannot manage this.