
Hi,
So I have this custom plugin delivered by one of our suppliers. Out of the box it executes without any Filtering Attribute. I found that it executes way too often with no reason so I decided to add a little filtering in the plugin registration tool.
After selecting the filtering attributes and pressing the update button, is there something else I should so (iisreset, pull the plug, dance around or drink a beer)? Because nothing changes at all. Even better, if I change it to only one attribute (which ofcours I don't change when testing the outcomes) the plugin still executes.
I have this feeling that I'm overlooking something very simple, but just can't see it (yet).
Any thoughts?
Thanks,
Jeroen
Jeroen,
Dancing around and drinking the beer for sure would not bring any harm so you can try it.
Now on serious note - I have never seen filtering works in the incorrect way. My assumption is that something (other plugin, workflow, something else) causes this plugin to trigger - turn on audit for entity and reproduce steps that should not trigger the plugin but triggers it in fact. Check the audit, find guilty, case is closed.