Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Here is my issue,
I have two plugins registered on quote entity:
2. Plguin 2 triggers on Activate button(OOB) of quote -> registered on setstate dynamic entity
They are both working fine when they are on 8.2
After V9 upgrade
if I click calculate somehow for no reason activate plugin is triggering and throwing error.
1. update plugin 2 to setstate message instead of Setstate dynamic entity -> result plugin 1 works but activate never triggers plugin 2
2. Disable plugin 2 -> result plugin 1 works
3. put plugin 2 in setstatedynamic entity -> run into same issue as stated
Any help appreciated. Thanks
During upgrade some of the plugin steps are creating duplicates, check for duplicates and delete/disable them
Check how many steps is there , in addition put the filtering attributes for the update plugins steps so that update plugin will be fire only when your fields will update.
The reason for your plugin is not getting trigger probably because it’s been registered on the SetStateRequest as we know that the SetStateRequest have been deprecated (Reference Link: https://docs.microsoft.com/en-us/previous-versions/dynamicscrm-2016/developers-guide/gg308277(v=crm.8)). We would rather suggest you, register the same plugin on the UPDATE message of the respective entity.
Hope this helps.
Hi Sreevalli, no duplicates were created but still the issue exists. Thanks for your reply I validated all my plugins for duplicates
Thanks for the response. Only one step is there on setstatedynamicentity, and filtering attributes is not supported for that
Hi Praveen ,
Create only update message steps for both the plugins and pass the filtering attributes instead of setstate.
I would like to close this thread with resolution:
In our pre-operation plugin we used to statecode, so we can use it for some validations. This caused the issue
context.InputParameters["Target"] = entity = proxy.Retrieve("name", <entity guid>, new ColumnSet("statecode"
later while updating entity this is failed since statecode and statuscode is taking negative values. later removing this from entity resolved the issue
Please click on yes of above helpful answer to close the thread. This will helps others in future.
I cant see Yes in it not sure why
You find after each answer like below , there is a Yes link.
Did this answer your question?
Business Applications communities