topic Re: Model States, Parameters & iProperties in Inventor Forum

Model States, Parameters & iProperties

NachoShaw — Fri, 21 Jan 2022 00:05:34 GMT

Hey

i feel like ive been here before but im going to ask, to see if anyone has a good resolution to this either natively or programatically.

Seeing as the preferred modelling route is from a base model, i have a base model. I also have a separate part that derives the base model parameters. In the separate part, i have some model states, each with a parameter named LENGTH.

Parameters

BASE MODEL: Param1 = 150, Param2 = 200, Param3 = 300

PART1: Linked Params = Param1, Param2, Param3

Part1: ModelState 1 - LENGTH = Param1

Part1: ModelState 2 - LENGTH = Param2

Part1: ModelState 3 - LENGTH = Param3

the Parameter LENGTH is set as exported so that i shown as an iProperty

when i review the iProperty per model state, i get the correct value based on the assigned value to LENGTH. For example@ ModelState2, LENGTH = 200.

When i place Part1 into an assembly 3 times, i change each instance to its respective ModelState. Then i can review each state and see the correct value assigned to Length.

When i review the assembly BOM however, it shows the name of the assigned parameter instead and NOT the value as seen in the iProperty LENGTH.

1. Why can we see the value in the iProperty but not in the BOM that reads the same iProperty?

2. How can i get the value to show instead of the Parameter name

Thanks

Re: Model States, Parameters & iProperties

BDCollett — Fri, 21 Jan 2022 01:34:03 GMT

It might depend how you are doing this, can you share an example?

I did a test based on what you said and the iProperty is coming across with a value in the BOM for each model state.

Re: Model States, Parameters & iProperties

NachoShaw — Fri, 21 Jan 2022 03:23:25 GMT

Hey

see example attached. Screenshot below explains the following

parameters in BM model
parameter assigned per model state
how the parameters are displayed in the assembly BOM with the component aded and each instance set to a different model state

i have set the parameter LENGTH in each ModelState as the respective parameter name to catch the value

Re: Model States, Parameters & iProperties

NachoShaw — Fri, 21 Jan 2022 04:22:59 GMT

Hey

It seems to work if i add ilogic like this

iProperties.Value("Custom", "LENGTH") = INT_LENGTH

where INT_LENGTH is a Parameter that is not exported.

It works but i feel that autodesk should resolve this seeing as Basel Model is standard development method, deriving parts from that base model is stadnard and model states are variations of a part most likely from a base model.

Re: Model States, Parameters & iProperties

johnsonshiue — Thu, 10 Feb 2022 20:38:05 GMT

Hi Folks,

I see the issue. This is a very interesting catch! The problem here is about how to present an exported parameter and the custom iProperty (expression vs value). The derived parameters are irrelevant here. I personally think this is a bug. It should work regardless. The BOM should show the proper value.

Let me work with the project team and see what we can do.

Many thanks!

Re: Model States, Parameters & iProperties

johnsonshiue — Fri, 11 Feb 2022 14:24:29 GMT

Hi Natchito,

Just a update on this issue. It has been reported as INVGEN-59847. We are investigating the issue and hopefully it will be fixed soon.

Many thanks!

Re: Model States, Parameters & iProperties

NachoShaw — Fri, 11 Feb 2022 14:40:27 GMT

much appreciated Johnson,

Thanks 🙂

Re: Model States, Parameters & iProperties

BDCollett — Wed, 02 Mar 2022 22:02:41 GMT

I just came across this issue myself, it's still there with recent patches.

A workaround seems to be that you just create a new custom iProp and have that reference the one you want. It will then bring through the parameters and not the equation.

Be nice to fix to get a fix though.

Re: Model States, Parameters & iProperties

NachoShaw — Wed, 02 Mar 2022 22:11:25 GMT

Are you saying that by creating another iProperty and getting the value from the iProperty showing the parameter name will show the correct value like

Base Model Param = Length = Param1 = 100in

Part linked Param = Length = Param1 = Param1

New iProperty = Length2 = Param1 = 100in

An established fix would be good

Thanks

Re: Model States, Parameters & iProperties

johnsonshiue — Thu, 03 Mar 2022 00:54:03 GMT

Hi Folks,

I just checked the latest status for INVGEN-59847. It has been resolved. It will be available on the coming 2022.3 update (April).

Many thanks!

Re: Model States, Parameters & iProperties

NachoShaw — Thu, 03 Mar 2022 01:09:55 GMT

Excellent news!

thanks 😃

Re: Model States, Parameters & iProperties

BDCollett — Thu, 03 Mar 2022 01:22:43 GMT

@NachoShaw wrote:
Hi

Are you saying that by creating another iProperty and getting the value from the iProperty showing the parameter name will show the correct value like

Base Model Param = Length = Param1 = 100in
Part linked Param = Length = Param1 = Param1
New iProperty = Length2 = Param1 = 100in

An established fix would be good

Thanks

Yes exactly! That seems to work from my tests.

You also need to push user parameters to custom iProps with iLogic if you want them to work as well.

Re: Model States, Parameters & iProperties

NachoShaw — Thu, 03 Mar 2022 04:32:18 GMT

Hey

@BDCollett wrote:

You also need to push user parameters to custom iProps with iLogic if you want them to work as well.

Which is pretty much what i show in my original post 😀

iProperties.Value("Custom", "LENGTH") = INT_LENGTH

Re: Model States, Parameters & iProperties

BDCollett — Thu, 03 Mar 2022 23:29:42 GMT

@NachoShaw wrote:
Hey

@BDCollett wrote:

You also need to push user parameters to custom iProps with iLogic if you want them to work as well.
Which is pretty much what i show in my original post 😀
iProperties.Value("Custom", "LENGTH") = INT_LENGTH

Yes going around in circles a bit there 🙂