- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I have an iLogic controlled assembly with sub assemblies that are also iLogic controlled. The main assembly calculates some lengths and turns some subs on and off and then updates all the subs. The subs also calculate some lengths and turn some parts on and off. I have a rule in both the main assembly and copies in the subs that control the LOD to make sure that it's set to custom before anything else runs.
Now I may be misunderstanding something, but it appears that it's possible to have a sub assembly set to one LOD but be referenced in a top level assembly as a different LOD. In other words I have a sub that shows in the top level browser as Master. If I open this sub and set it from within the sub to custom LOD and switch back to the top level assembly it is still set to master there. It appears that this is what my LOD rule is also doing, setting it to custom in the sub but not changing the top level reference.
Am I misunderstanding something here? If not, does anyone have an iLogic snippet I can use to change this "referenced LOD" before the rest of my code runs?
Thanks in advance,
Mike

Solved! Go to Solution.