2
Hi,
We have created a custom entity which has a reference to an opportunity.
When the opportunity closes, we need to change the status of the related custom entity records to Inactive.
It is however not clear for me on what plugin entity/message I could react.
Opportunity - SetState or OpportunityClose - Create(?).
What would be the best option, and why would one option be preferabel over the other?
*This post is locked for comments
Birgit,
Potentially you can use workflow to handle change of opportunity state and cascade change of status to children using one of steps from my workflow toolkit - github.com/.../releases - you will need Relashionships - Cascade Status.
Also if I'm not wrong you can resolve that task using relationship configuration itself because there is no setting to configure cascade of state/status.
why don't you configure this in the relationship mapping between the opportunity and your custom entity? That would be the easiest method I would think
Hello Birgit ,
If you require to write a plugin on stage change then user ."SetstateDynamicEntity" message
Hi,
I'd just try registering that plugin on the "Update" message for the opportunity entity - you will need to have a condition in your plugin code to verify if statecode attribute is in the "Target", and, then, to verify the specific value of the statecode (0 would be active, anything else would be closed)
As to why, SetState request is deprecated:
msdn.microsoft.com/.../microsoft.crm.sdk.messages.setstaterequest.aspx
Why not on the OpportunityClose entity.. You can probably do it on the "Create" of that entity, too (if it allows for the plugins/workflows to be registered)
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,214
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (