Feature FIX: Exclude Parameters from Model State

Feature FIX: Exclude Parameters from Model State

6.Day.Old.Filet-O-Fish
Enthusiast Enthusiast
359 Views
3 Replies
Message 1 of 4

Feature FIX: Exclude Parameters from Model State

6.Day.Old.Filet-O-Fish
Enthusiast
Enthusiast

We have been building 'configurators', top-level assemblies that engineers can make a customized, bespoke assembly through a few short forms, and export. Previously we had worked in Inventor 2020 so we were eagerly awaiting the upgrade to 24 to play with Model States. They work really well, except when they break everything. The fix should be easy but isn't on our side.

 

A handful of parts require custom values. Here's where the issue lies... Those custom values had previously been driven through User Parameters from a Form. Model States now saves these in a spreadsheet each time one of these changes, and will revert to that value when the state switches. I don't want certain parameters to be linked to the Model State AT ALL.  But if I only use parameters i create inside iLogic code, they cannot be accessed through the Forms...

 

We need to be able to EXCLUDE parameters from Model States. Until then, a feature that would otherwise significantly speed up our workflow is actually a trap that cannot be used.

0 Likes
Accepted solutions (2)
360 Views
3 Replies
Replies (3)
Message 2 of 4

CCarreiras
Mentor
Mentor
Accepted solution

Agree... one of the major flaws that prevents the use of model states in some cases.
As an workaround, after all the configurations, enable all scope edits to have the custom values.

CCarreiras_0-1712620672442.png

 

CCarreiras

EESignature

0 Likes
Message 3 of 4

6.Day.Old.Filet-O-Fish
Enthusiast
Enthusiast

huh, this isn't what I expected that to do. I thought it would've edited the value in all Model states to be the same but it doesn't add the value to the excel doc at all, which is actually just what I needed.  I'm not really sure why this works but good catch. 

0 Likes
Message 4 of 4

CCarreiras
Mentor
Mentor
Accepted solution

Now, you have to pay the attention that the "non custom" values doesn't should be changed by the form, they should be at the proper row in the excel, and always fixed... i think you get it.

CCarreiras

EESignature