Hi,
What are the disadvantages of recursive workflow in ms dynamics CRM online?
I want to delete 10,000 records every day at 5:00 AM from 10 entities in crm.
Thanks,
Pavan N
*This post is locked for comments
Hi,
What are the disadvantages of recursive workflow in ms dynamics CRM online?
I want to delete 10,000 records every day at 5:00 AM from 10 entities in crm.
Thanks,
Pavan N
*This post is locked for comments
Ok, with every response, there is a new info getting uncovered. Lets mention them in the question itself so that if anyone who is new to this discussion can come and pitch in his ideas.
As for this, if you have to delete the records then you might as well take a look at the bulk deletion job mentioned above or what Ravi has suggested.
Does this help?
Thanks for your reply,
We are using CRM for UK. In UK, we have GDPR. For GDPR we have to delete all the records from CRM.
Thanks,
Pavan N
Have you consider using recurring Microsoft Flow i.e. which runs on a daily bases and then select all the cases which are olderthan 365 days and then delete it?
Thanks for your reply..
I am not able to convert my workflow in to Async process. In the workflow using "Timeout until" for waiting purpose.
Thanks,
Pavan N
Now it makes much more sense. Thanks for sharing this info.
Coming to the point, I would rather not delete those cases from Dynamics, instead have them archieved just in case you need them for building up a KB. My recommendation here would be to take a look at the Micrsooft Labs solution for data archival appsource.microsoft.com/.../microsoft_labs.dataarchival
This should be a better fit for this requirement.
Thanks for your reply..
I am using case entity as a primary and I want to delete the cases which are completed 365 days. I have to check this every day and delete the cases and also related entites data also. The case is having nearly 10 related entities. Like email,tasks, social and etc..
Thanks,
Pavan N
Hi,
Do you already have a workflow which runs recursively and delete 10,000 records everyday at 5 AM. I don't even think that it is possible to achieve this requirement with just workflows cause recursive workflow the workflow is calling the workflow itself and workflow runs on a record. If you are running a workflow on a record which you are deleting, then it won't run next time.
If you could share more details about your implementation/ requirement, I am sure there must be some other better way to achieve this.
To answer your question (and assuming that you do have some workflow which you want to run recursively 10K records on 10 entities), you will face performance issue with several different components of crm,. i.e. if you have other workflow then they will also start going into waiting as they will not get enough resources to execute. If you have email configured using server side sync then it may also impact. If you have rollup fields then these may also impact. In short, having so many workflow instances running at the same time will cause any service to fail/ slow down which uses async service.
Hope this helps.
Hi Pavan,
I believe you are aware Asynchronous workflow is execute by the CRM Async Service. I dont think this will going to impact the performance of the your CRM application.
Is there any specific reason you are not using OOB bulk delete operation and schedule it?
community.dynamics.com/.../tip-346-scheduling-daily-bulk-delete-jobs
I would refrain from writing any workflow for this, instead, leverage the out of the box feature of Bulk Deletion Job (docs.microsoft.com/.../delete-bulk-records).
Having said that, I want to ask if there is a need of deleting records on a daily basis then why are those records there in CRM in the first place?
André Arnaud de Cal...
292,516
Super User 2025 Season 1
Martin Dráb
231,409
Most Valuable Professional
nmaenpaa
101,156