Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.
e_frissell
in reply to: WCrihfield

Thanks, I'll take a look and as always I really appreciate your help and been feeling a bit guilty that I haven't been great about getting back to you - been having a lot of 10~20 hour projects recently which has me trying to figure out iLogic solutions to small problems and then encountering something totally different 2 days later.

 

Regarding the model states you are right that model states were involved however I'm positive the constraints were equal - they were a pair of doors and the constraint was set by the distance between a right and left side hinge, then again with a symmetric constraint across one of the planes.  What happened was that in the main assembly distance from one hinge to the symmetry plane was different than the other side although in the sub-assembly it was correct. The fix for this was that I added 1" to the distance between the hinges, then removed that inch, and it was enough for the main assembly to note the sub-assembly had changed and it fixed it.

 

Anyways, going through that documentation, each states that it does a compute operation on "all entities within the Document's scope" - would the entities of a sub-assembly be considered a "entity" of the parent document?  If yes it seems rebuild would force everything to update, if no then it seems like a loop would be required?

 

From looking at my script again running update2 and rebuild2 in consecutive lines might be a bit redundant