CODEWITHSUNDEEP
dynamics-crmworkflowcrm
Tliashev.FF
Tliashev.FF

Reputation: 35

CRM Dynamics workflow not triggering for all records

Problem: Set up a workflow in CRM Dynamics 365 Sales that starts when the value of a specific field changes. But it turned out that the process does not start if changes are made to old CRM records (which were created before starting the process itself).

Question: Is there any method how can I make CRM start the process even for old records? I am sorry that everything is in Russian. I work in this version. The process works correctly when creating a record and when editing a field in a new record. And when editing a field in an existing record, the process does not start

enter image description here enter image description here

Upvotes: 2

Views: 2388

Answers (4)

Jens.F
Jens.F

Reputation: 41

It seems to me that Microsoft has now built a bug into Dynamics365 CRM. It used to be possible to trigger workflows based on field changes without any problems. Unfortunately, it no longer works today, even if Organization is set. As a workaround, you can build a Powerautomate flow that triggers on the field change and then calls a CRM action, which then starts the desired workflow at the end. It would be great if Microsoft would correct the functionality in the workflow, because this workaround is very cumbersome and uses up unnecessary resources.

Upvotes: 0

Arun Vinoth PrecogTechnologies
Arun Vinoth PrecogTechnologies

Reputation: 22836

To make that Workflow to trigger on all records, make the scope as “Organization” instead of “User” - it should work as intended. Read more

It’s not about when it is created, probably those records are owned by somebody else. That’s why user scoped WF is not triggering at all.

Upvotes: 1

AnkUser
AnkUser

Reputation: 5531

You do not need to do any manual update. The workflow you creates should be enough to kick in. make sure your workflow has trigger on change of field. Screenshot for reference. It does not matter when the Workflow is created. As long as it satisfies condition it will kick in.

enter image description here

enter image description here

Upvotes: 0

Renjith
Renjith

Reputation: 765

Normally workflows trigger any future relevant changes. Otherwise, we should create a scenario where we cause that trigger. A couple of options,

  1. As you have already set the workflow to run on a specific field change, you can make an update to that field and save the record which should trigger the workflow. If it's a very less number of records it's possible otherwise it's not a good idea to manually update all these records. If you don't want to do this manually you can update the records using any other option like a console app which makes updates to all the records (this would be faster assuming this is a one-time activity you have to do.)
  2. Make this workflow on demand and trigger the same manually for all the records you want to run the workflow. Again this is a manual process but cleaner than the first one.

Upvotes: 0

Related Questions