iLogic rule not firing on linked parameter change

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I'm experiencing some strange behavior that I've never had a problem with on previous Inventor versions.
I'm using a multi-body base component and driving its parameters from a high level assembly. I also derive/link the parameters of the base component into parts and assemblies for use inside iLogic rules within those files.
For the most part, a change to a parameter in the base component will trigger any rules in parts and assemblies where the parameter is linked. However I have a few instances where this doesn't happen.
For testing purposes, in Assembly2.iam and Assembly3.iam I have this rule:
msgbox(FREE_AIRLINE_DIA)
In both of those assemblies the base component parameter is linked through the Parameters dialog as shown below
From my high level assembly I use the iLogic form to change the value of FREE_AIRLINE_DIA in the base component.
To do this I use this rule in my high level assembly:
Parameter(“BaseComponent.ipt”, "FREE_AIRLINE_DIA") = FREE_AIRLINE_DIA
The parameter successfully changes in my base component and naturally in my two assemblies also, but only the rule in Assembly2.iam gets triggered
Any suggestions as to why this is happening?
Both rule options are set to run automatically.
Something interesting to note is, if I manually go into the base component and change the parameter, rather than driving it from my high-level assembly rule, when I open the assembly that's not working, there's a pending Inventor update (due to the linked parameter value change) and once I click it the rule will run. So the rule is running automatically on the parameter change, just not when I do it using the way I want to from the high level assembly iLogic form.
I also experience the same issue in a part file, with a different parameter, but have managed to work around it by assigning the rule to the Part Geometry Change event trigger.
As I mentioned before, I've used this methodology many times in the past and this is the first time I've had this problem. Its frustrating the life out of me that I can't get down to the bottom of the issue. Not ideal when your under pressure to get work released
Any help would be much appreciated!