Model States and iProperties

[aaronbreaux]

We are just getting into model states and I have ran into an issue and am unsure if this is just how it is or might be something else.

We would like to use model states for different configurations of parts and want to use the one part file but use seperate dwg files for each configuration. The problem I am running into is I am unable to change the information on the status tab (status, approved by & date, etc) of iProperties. I can have unique values in the Project tab (part number, description, etc).

Primary iProp status

Changing the status iProps for the child (Status field deleted for this example)

Primary is now also changed (Status deleted)

[rhasell]

That is odd,

I have not tested all of them, but so far it only happens with "Status", everything else that I tested worked. I tried with multiple Model states, with the same result.

I guess one work around is to use a different iProperty, or create a custom property for the moment.

[johnsonshiue · Accepted solution]

Hi Aaron,

Those properties are per document basis, not per Model State basis.

Many thanks!

[rhasell]

Thanks for confirming, I suspected as much.

[aaronbreaux]

Any particular reason(s) why?

[johnsonshiue]

Hi Aaron,

It is a limitation. Though, each member is like a mini doc within a doc, we don't want to get into the business of micromanaging mini docs. It can be messy. Those document specific property will have two levels: main do and mini doc. It can get very confusing for file managing system to tell which property is calling the shot.

Many thanks!