Balloons not linking to model state iproperties

Balloons not linking to model state iproperties

tmathieson
Advocate Advocate
684 Views
3 Replies
Message 1 of 4

Balloons not linking to model state iproperties

tmathieson
Advocate
Advocate

Hello again,

 

i am having an issue with model states (seem to have a few) and balloon.  i have a part that has 5 or 6 model states, each with has their own custom iProperty, say "label_value".  when i add different model states to a drawing and go to label or add a balloon, which are link to the custom prop, i get different results.  the labels parse the uprop correctly, but the Balloon  says "Varies". see attached.

 

if i change all model states to the same one, the Balloon work as it should.

 

how do i tell the Balloon to only read the Iprop of the model state it is attached too

 

thanks in advanced!!

0 Likes
685 Views
3 Replies
Replies (3)
Message 2 of 4

Gabriel_Watson
Mentor
Mentor

Is your drawing view using the Master model state or a specific custom one?
I cannot test it right now, but try picking one specific Model State that is not master for the views, and see if that narrows it down to one value to be shown:

Galaxybane_1-1643918522339.png

 

0 Likes
Message 3 of 4

tmathieson
Advocate
Advocate

Hi, thanks for your reply.

 

i am using a model state that is not master... still not working as it should.  i think "model states" need a lot of work.  this is a simple thing that should not be causing these issues.  why have iproperties that are unique to a model state if they can't be used....

 

and i am afraid, as is often the case,  we will need a 'work around'....

 

 

0 Likes
Message 4 of 4

johnsonshiue
Community Manager
Community Manager
Hi! Let me ask you one thing. How are the part custom properties changed? Are they captured in the individual Model State within the part? Or, you use iLogic to drive such change? If it is former, it should work. Please share the files that exhibit the behavior here.
If it is latter, it is working as design. It is because the iLogic's change isn't captured on the table. Model State specific change should be captured on the table (member scope). Otherwise, it applies to all Model States (factory scope).
Many thanks!


Johnson Shiue ([email protected])
Software Test Engineer
0 Likes