Event Triggers not firing in Inv Server (Configure 360)

[clutsa]

This is a repost from https://forums.autodesk.com/t5/configurator-360-forum/event-triggers-not-firing-in-top-level-assembl... and I attached the bare bone (.zip) model I talk about below. I know configurator 360 uses Inventor Server so anywhere I say C360 just imagine I said Inv Server. If anyone out there can help me figure this out I'm getting desperate. 

Once upon a time in a land of innocence, I used to trigger rules in my top-level assembly by offsetting a plane by a distance set in my skeletal model. When the skeleton would change the parameter would update and the "Any Model Parameter Change" event would fire my rule. (This story probably sounds like one you've heard me tell before; Same story different day)

I stripped my scenario down to the bare bones. 

https://configurator360.autodesk.com/125106773177157182/thcsr5q4ykx8 I have one parameter in a, new from scratch, skeleton that has a multi value of 1 thru 4. I have one part in a, new from scratch, .iam, a plane offset from origin, and a rule that toggles visible/exclude set to run on parameter change (it doesn't care what has changed just that something has changed.) It works just as I would expect in Inv 2018 but does nothing in C360. Oddly in the model I care about the sub parts are set to run the same way and work but when I put my new single part assembly in another assembly it still doesn't fire (in C360)

I have been fighting this since July 9th. Why doesn't this work anymore? No event triggers I set with the event triggers dialog trigger anymore. Did something change in the last 4 months? I know C360 was updated to 2020 and support was dropped for 2017 and older but why do my old saved files work and new saved files don't?

[HermJan.Otterman · Accepted solution]

Hello Andrew

https://configurator360.autodesk.com/345372262422312037/mw99g2bn6llh

is this what you need?

I made a form in you TestSkeletonTriggers.ipt

I added you TestSkeletonTriggers.ipt (= Master) to the assembly

uploaded it to C360, with the option "Assembly with Skeleton"

[clutsa]

@HermJan.Otterman I am unable to follow your link but down loading the zip and uploading to my C360 page it is now working. I'm I understanding that all you did was make the form and added the skeleton as a part in the model tree of the assembly? I've never had to do that before but if that is all it takes I'll try it.

[HermJan.Otterman]

that is correct.

creating the form is not Necessary, but the most easy.

I always add my masterfile to my assembly

maybe the link is blocked somehow, I have changed it to "Unrestricted viewing"

let me know if you get it working this way, thanks

[clutsa]

Your link works now. It acts as I would expect.

I added my skeleton into my top-level assembly like I would add any other part. Saved the assembly and skeleton and zipped them and loaded them in C360 and got nothing. Is there a "special way" or setting to add the skeleton to the top-level?  

[HermJan.Otterman]

I made you a screencast, this shows the steps I took.

I hope it helps, let me know

https://autode.sk/32wL2a3

[clutsa · Accepted solution]

Thank you for your help! I have managed to replicate your results in the example file I uploaded. I made the same changes to my actual product and still had no luck. I'm not sure what I did to my files to make them stop working but I really angered the Gods of Inventor.

I ended up adding the below rule in my skeleton file (for my actual document) and calling it at the end of another rule that updates some parameters and the top-level assembly rule is now firing (it still has a couple of errors that didn't present in Inv.)

Dim app = ThisServer
Dim childDoc As AssemblyDocument
Dim myDoc As Document
Dim iLogicAuto = iLogicVb.Automation

For Each myDoc In app.Documents
		If myDoc.DisplayName = "Top_Level_Assembly_Name_Here.iam" Then
			childDoc = myDoc
			Exit For
		End If
Next
If Not childDoc Is Nothing Then
	iLogicAuto.RunRule(childDoc, "MyRuleNameHere")
End If

I still don't think that I should need this work around but it gets me moving again. 

[HermJan.Otterman]

Nice that it works.

I also notice that C360 is more sensitve than Inventor, somtimes I also have no problems in Inventor but C360 crashes. what is helpfull then, is the log file in C360 that indicates where the error can be found.

for one of my C360 projects I copy files on the C360 server and than place those files. the triggers for those parts don't work. (in Inventor they do), so now after all parts have been placed I change a value in My master to change and trigger/update all the parts....

[clutsa]

That's what I was trying to do (and have done successfully in the past.) That's why I had one parameter linked to the skeleton. I could change the parameter in the skeleton that changed the linked parameter in the top-level assembly that was used to control the offset of a plane and that triggered the "on parameter change" event trigger to run my rule. Something broke somewhere and that event trigger doesn't fire in C360 anymore... I just don't know what broke.