topic Re: iProperty value in assembly does not match value in part [modelstates] in Inventor Forum

iProperty value in assembly does not match value in part [modelstates]

J-Camper — Fri, 29 Mar 2024 15:58:43 GMT

I'm experiencing an issue where the iproperties for a part component do not match the property value of the part itself. I have a custom iproperty with the equation "=<Material>". I've figured out a better way to what i intended, but i still want to bring up the issue.

Issue:

iProperty correct when checking with part openiProperty incorrect when checking from assembly open

I checked the value in the part and it is correct, but when you check the same property in an assembly it is incorrect. I have no idea what would be the cause of this. Rebuild all does nothing to change this behavior.

Anyone have any thoughts?

Re: iProperty value in assembly does not match value in part [modelstates]

johnsonshiue — Tue, 02 Apr 2024 00:21:36 GMT

Hi! I suspect this has something to do with Edit Scope setting. When you leverage iProperty expression, you need to make sure the Edit Scope is set to Edit Factory, not Edit Member. Otherwise, it will literally take the "expression" and populate it on the table.

Try this. Edit the Model State table in Excel and remove the particular custom iProperty column. After that, set Edit Scope to Edit Factory. Then activate each member. The iProperty will update correctly accordingly.

Many thanks!

Re: iProperty value in assembly does not match value in part [modelstates]

J-Camper — Tue, 02 Apr 2024 21:17:58 GMT

@johnsonshiue,

Thanks for the response, but I don't think that was the issue. I had the same expression set for every modelstate. I also noticed the issue with the native Material iProperty, not displaying properly in my drawing views.

I was able to get the material to propagate through by initiating "edit-in-place" for each component, and switching material away and back to my intended material. I didn't check after entering "edit-in-place" alone to see if that was enough, or if it truly needed the material toggle while editing in place. Once I completed this and checked my properties, both the custom iProperty and the drawing leader, referencing the native Material property, were correct and in sync.

It seems weird that rebuild all did not trigger the native Material Property to update in my drawing view. It feels like maybe something is getting hung up when updating modelstate components in assembly after making changes to the modelstate file inside the part itself.

Re: iProperty value in assembly does not match value in part [modelstates]

johnsonshiue — Wed, 03 Apr 2024 00:26:02 GMT

Hi! If possible, please share the files in zip with me directly johnson.shiue@autodesk.com. I would like to understand the Model States iProperties behavior better.

Many thanks!

Re: iProperty value in assembly does not match value in part [modelstates]

J-Camper — Wed, 03 Apr 2024 12:58:02 GMT

I did check a version into the vault when it was not working properly. I will pull that version back to my computer and get it packaged up. I was trying to reproduce it last night with a simpler assembly/drawing but it was responding better to updates so I'm still not sure exactly what was happening.

It did get a similar issue at first when I made a material change to all modelstates by switching to factory edit and changing the material once, instead of on each modelstate individually. The simpler drawing did show the wrong material when updating the drawing alone, but updating the assembly fixed it in that test case.

Re: iProperty value in assembly does not match value in part [modelstates]

J-Camper — Wed, 03 Apr 2024 13:36:09 GMT

@johnsonshiue

i could not email the files, so i tried to share them from a onedrive folder.

Let me know if you don't get them

Re: iProperty value in assembly does not match value in part [modelstates]

J-Camper — Wed, 03 Apr 2024 14:22:16 GMT

@johnsonshiue,

By the way, drawing views 05/SD-10.3 & 06/SD-10.3 have material leaders to 2 different modelstates of the part "8210-SD10-DOR-SLAB-10-01.ipt", and the leader result does not match the material in the model.

Re: iProperty value in assembly does not match value in part [modelstates]

johnsonshiue — Fri, 05 Apr 2024 01:53:36 GMT

Hi! I have taken a look at the files Jeff shared with me. Without disclosing the detail, I can share the findings as the following. Indeed, the material style shown in the leader text is out of sync with the part. It is unclear to me how it happened. There is a way to "fix" it however. Open the part and go to Manage -> Rebuild All. Open the assembly -> Update. After that, the material style will be corrected in the drawing.

This step should not be necessary. Whenever Rebuild All helps, it means there is inconsistency. Unfortunately, we don’t know how the corruption happened. Something was out-of-sync somehow.

Many thanks!

Re: iProperty value in assembly does not match value in part [modelstates]

J-Camper — Fri, 05 Apr 2024 14:10:12 GMT

@johnsonshiue,

I'm not sure that truly fixes the issue as i was not able to fix it this way after reproducing the issue. I was trying many things before i logged the vault copy.

Rebuild all from assembly
Rebuild all from part files
Update design from Task scheduler

I'm not sure what fixed it the first time, but I have been able to reproduce the issue using this same files i shared. I've found that if i simply Factory edit change the material, then nothing updates correctly, and in fact i have to do this process to fix the issue after doing that:

Member edit material change to material i don't want
- for some reason going directly to the intended material was not consistent in my testing
Member edit material change to material i want
Factory edit Rebuild all
Repeat for all Modelstates that need to change

Additionally, when i exited after applying changes to the final modelstate, the component referencing the last active modelstate did not update properly. I'm not sure if my fix was the only way, but i ended up going back into the part and applying the same process to the primary modelstate, which isn't referenced in my assembly at all, so it doesn't matter if that one updates properly, in this case at least.

All this was reproduced entirely void of any ilogic running. I have also embedded a screen capture i took of the entire reproduction and fix process:

(view in My Videos)

Re: iProperty value in assembly does not match value in part [modelstates]

johnsonshiue — Mon, 08 Apr 2024 01:56:33 GMT

Hi! I cannot seem to reproduce the behavior on my machine. Instead of changing the Edit Scope back to Member Scope, keep it in Edit Factory Scope. Make sure the values are indeed updated correct in the iProperties dialog and the drawing. Then change the Edit Scope. I suspect there could be a timing issue.

Many thanks!

Re: iProperty value in assembly does not match value in part [modelstates]

J-Camper — Mon, 08 Apr 2024 13:12:17 GMT

@johnsonshiue,

It is interesting you don't seem to get the same results I do. I was using 2023.4.1 up until the end of the week when I saw the 2023.4.2 update. What version were you testing with?

Re: iProperty value in assembly does not match value in part [modelstates]

johnsonshiue — Tue, 09 Apr 2024 23:49:42 GMT

Hi Jeff,

I thought you were on 2024. I tried it on 2024.2.1 and 2025. Let me try it on 2023 and get back to you with my findings.

Many thanks!

Re: iProperty value in assembly does not match value in part [modelstates]

johnsonshiue — Wed, 10 Apr 2024 00:11:29 GMT

Hi Jeff,

I tried the exact same workflow on 2023.4.2. I still see the same behavior as 2024 and 2025. I think the key step here is to keep the Edit Scope as Factory Scope until the properties have been propagated to the drawing properly. Could you try it and see if it works for you?

Many thanks!

Re: iProperty value in assembly does not match value in part [modelstates]

J-Camper — Wed, 10 Apr 2024 15:36:49 GMT

@johnsonshiue,

I'm still getting inconsistent results with the simple approach you are saying works on your end. I tried in several different drawing/assemblies. Some are responding the way you see them happening, while other continue to persist as I'm seeing with the data set I shared with you.

I still find it weird that when i don't see the Material iProperty update, i do see the drawing Hatch change immediately, and the Physical Properties Material is displaying the correct value. It seems like some parts of the part is getting updated instantly, but just not the whole thing. I was able to write an ilogic rule that makes my more complicated process occur, just as quickly as the simple process you suggested.

I will mark this as complete, and include the ilogic rule that makes my process quick, incase anyone ends up with the same issue my team has been seeing.

Thank you for your help and time looking into this for me.