You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi guys, let me know if this is an error on my part or this is indeed a bug.
Expected behaviour
I use FakeXrmEasy in pipeline simulation mode. I want to trigger a plugin when multiple accounts are retrieved, so I register my plugin step on the RetrieveMultiple message on the account entity:
My TestPlugin triggers and starts running its Execute method.
Actual behaviour
My TestPlugin does not trigger. I debugged using the JetBrains decompiler and it does not retrieve any registered plugin steps for that request.
Current workaround
I found that it does work when I register the plugin step without the EntityLogicalName, so:
But I can't imagine this is intended behaviour. When registering a plugin step on the RetrieveMultiple message with the Plugin Registration Tool, I do set a target entity. Not being able to set one also implies that the plugin is triggered for any RetrieveMultiple request, which is perhaps a bit excessive.
The text was updated successfully, but these errors were encountered:
Thanks for investigating! I am using a non-commercial license and I have a workaround for now since my UTs are seperate for each entity. So by all means, fix this when you have the time. :)
Hi guys, let me know if this is an error on my part or this is indeed a bug.
Expected behaviour
I use FakeXrmEasy in pipeline simulation mode. I want to trigger a plugin when multiple accounts are retrieved, so I register my plugin step on the RetrieveMultiple message on the account entity:
Then, after I initialize my environment with one or more account records, I execute a RetrieveMultipleRequest:
My
TestPlugin
triggers and starts running itsExecute
method.Actual behaviour
My
TestPlugin
does not trigger. I debugged using the JetBrains decompiler and it does not retrieve any registered plugin steps for that request.Current workaround
I found that it does work when I register the plugin step without the
EntityLogicalName
, so:But I can't imagine this is intended behaviour. When registering a plugin step on the RetrieveMultiple message with the Plugin Registration Tool, I do set a target entity. Not being able to set one also implies that the plugin is triggered for any RetrieveMultiple request, which is perhaps a bit excessive.
The text was updated successfully, but these errors were encountered: