On my local dev machine and our demo servers this works like a charm, everything gets called as it should be.
However when I deployed the AddIn to a customer system (BC140, OnPrem, WebClient) I noticed that the usercontrols triggers are not called.Info:
The customer system has been upgraded from 2016 -> 2018 -> BC140 over the last years. There are no visible errors on the client when displaying the AddIn. Eventlog does not show anything regarding the issue. InvokeExtensibilityMethod is only called in the StartupScript.Questions:
What could possibly cause this behaviour?
Are there any config parameters that would explain this?
How does InvokeExtensibilityMethod actually work? Where is it implemented?
Is there any way the upgrade(s) might have gone wrong to cause this?
Could this be a WebClient / IIS configuration issue?
I'm glad for any input. The issue has been plaguing me for quite some time now.