iLogic driven subassembly does not visually update

[Anonymous]

Hello all! 

This is my first post at these forums so please correct me if I do something wrong.

A little background before we start with the hard part. This is the first project in which I use iLogic, I did not follow a course for iLogic so far everything I learned by either doing or through reading this forum. was using Therefor the coding I used may be a little bit of a mess, but that will be the next step. Version used is Inventor Professional 2018. If anything is missing or if anyone wants to know more please do not hesitate to ask me.

Now for the hard part;

I have an iLogic driven assembly of a steel structure (not purely a machine, not purely a frame) with iLogic i control the size of the sub-assemblies in the main assembly and further more the parts within the sub-assemblies. This all from the main assembly. This all worked perfectly fine until for some undefined reason one of the sub-assemblies decided to no longer visually update in the main assembly, while (when opening the sub-assembly) it is changed. 

Steps/solutions tested so far (without result);

- Checked the levels of detail in the sub-assemblies and main assembly (all set to Master now)

- Checked representations in the sub-assemblies and main assembly (all set to Master now)

- Deleted the sub-assembly from the main assembly and inserted the same again

- Debugged the code by strategically placing message boxes around the code 

- Moved code from the main assembly to a lower level sub-assembly

- Searched the forums

The result however stayed the same. The sub-assembly has changed to the new set of parameters when opened from the browser of through the main assembly, but it is not visible in the main assembly.

Is there anyone that has experienced this as well?

Best regards!

[johnsonshiue]

Hi!  The behavior does not sound right. If possible, please share an example here. Forum experts can help take a look to understand the behavior better.

Many thanks!

[Anonymous]

I'm sorry for the slow response. Due to in NDA between my employer and the customer I can't share anything, as everything little detail is property of the customer. 

But i found out the issue, but no stable fix for it. I will try to explain it textual as best as possible. It turned out as a representation issue when I reconfigure the main assembly through an iLogic form.

There are two representations defined; 1. Master (which is locked) and 2. Default (the one it should be). Somehow some (not all) subassemblies switch from default to master in this case. When I manually switch them to default everything is correct.

Is there a way to always force the default representation?

[johnsonshiue · Accepted solution]

Hi! You can either use iLogic rule to enforce that. Or, you change the File Open Options (Tools -> App Options -> File -> Open Options -> select the appropriate Design View Rep for each file type). This will help you place or open a part/assembly in the desirable Design View.

Many thanks!

[Anonymous]

Many thanks to you! 

We choose to force the right representation with an iLogic rule as we deemed it most stable for us.