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.
2022 Release Wave 2Check out the latest updates and new features of Dynamics 365 released from October 2022 through March 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I have thousands of opportunities where the cascading rules have caused them to be assigned to incorrect people. I have now removed the cascade all option.
I want to update all opportunities so that the owner is set back to the person who originally created the opportunity.
1) Perform an advanced find and then run an on-demand workflow to change these. You cannot do this because in the advanced find you cannot compare two fields. E.g. Owner does not equal ....enter value (can't put a field here).
2) Run it in SQL - Simple to do but I believe this is completely unsupported due to anything else this is all linked to and other cascading rules could potentially cause further problems on other entities.
Does anybody have any other suggestions?
I thunk ssis package or consol application required to update owner back to required person..
You can do it in custom workflow activity also..
Create a on demand workflow and add a step to compare owner does not equal created by then in the next step assign opportunty to created by.
You can bulk workflow tool to run the on-demand workflow on all records and it will update owner only when conditions are met
I also would suggest you to create a On-Demand Workflow & follow the steps described by Chitra.
Thanks & Regards,
Create an on-demand workflow and apply it for the set of opportunities which you need to update. This is the easiest way.
Yes I had already created this workflow but it was slightly different to yours. I used the query:
If opportunity:createdbyequals user1 AND opportunity owner does not equal user1 then
Assign opportunity to User1.
I was then going to run this workflow for each user. Do you think yours would be better than this?
Your condition also should work fine. I just took example it's up to you to add condition to get expected result
Business Applications communities