iPart reverting when switching between model states

[kristin.jakuszanek]

When trying to get views set up on an install print I am putting together I noticed on of my Ipart 'duct' segments not holding the size I am setting it to when going between model states. 

In the video you will see I have a section I keep making 25", I will save and change model states and the part will revert back to the original size (17.18"). I can change it again to 25" in the new model state, and switch to another and again, it will revert, even though it shows its updating as a new part. 

Is there a known issue in 2022 between Iparts and model states? I never had this issue in 2020 when we were utilizing LODs. 

I am running Build: 350, Release: 2022.3

[johnsonshiue]

Hi! Is this a custom iPart or a regular iPart? When you mentioned that you set it to 25", did you check and see if it is captured on the Model State table? I would think it was not. Any cross-part or cross-level association isn't captured on the Model State table.

To make this case work, you will need to have two members in the iPart (25" and 17"). Change the member accordingly. If you cannot figure it out, please share an example here. Forum experts can help take a look.

Many thanks!

[kristin.jakuszanek]

Johnson, 

They are custom Iparts so they never had a table list for every size possible, but are set to be a custom length we input as we place them into our assemblies. I have attached a video to show how you are prompted when placing a piece. When a new piece is placed, or an existing piece is renamed it will give it a new number and when the assembly is checked into the vault the custom iparts go into the engineering folder we have set up in there. The issue that I started noticing when we switched to 2022 is that sometimes when you change an existing custom ipart, it will not hold the new saved changes when switching between the model states (as shown in the original video on the post).

I have also had older assemblies that I open in 2022 to work on that had been initially created in 2020 and a lot of the custom iparts will renumber themselves to 0 or show no number and need to be essentially replaced into the assembly so they show their correct length again and be allowed to check in without giving a duplicate name check in error. 

Below are some of the setting within one of the custom iparts

[johnsonshiue]

Hi Kristin,

I think I know this behavior. The issue here is that when you change the custom parameter value in an iPart, such parameter change isn't captured on the hosting assembly Model State table. Although the table replace column is added, the actual custom parameter value isn't captured. As a result, it is treated like replacing itself. I believe you would the same behavior in iAssembly also. This is currently a limitation unfortunately.

Many thanks!

[kristin.jakuszanek]

Do you know if there is a plan to correct this behavior in an upcoming update? The only way I have found to correct this issue is just completely replacing the component doing a 'replace from vault'.
While this work around is working for now, it is more cumbersome than just being able to have the part adjusted in assembly as I was able to do before.

[johnsonshiue]

Hi Kristin,

We are indeed aware of the request. But, it is not currently on our radar to resolve. There are multiple workflows to be enabled here. Please feel free to report it as an idea on Inventor Ideas forum (https://forums.autodesk.com/t5/inventor-ideas/idb-p/v1232).

Many thanks!