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 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
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
We have at least two workflows that changed trigger behavior yesterday. They have been in place for years without any changes to the triggers. Both are set to trigger upon record creation and field change. Starting yesterday, they have been running twice when the triggering field is populated upon creation. Previously, if a field was populated upon record creation, it didn't register as a field change for workflow trigger purposes.
For each instance where this is happening, one process session/job shows the start reason as "Record was created," while the other shows "Record field changed." Meanwhile, the audit history shows only a single event - create - that includes the value populated for the field. So I'm fairly certain there has been a change in workflow trigger behavior, where field change upon creation is now considered a field change for workflow trigger purposes.
I'm wondering if anyone else has noticed this, and if it is an intentional change by Microsoft that will remain in place. If so, I can remove the creation triggers on my workflows to avoid duplicate runs, but I'm reluctant to do so if the behavior may change again.
Ah! Session per field! We've been wondering why the multiples but, it's not new.
It is new for us! Up until yesterday, when a record was created, no field changes were recognized for workflow trigger purposes. Field changes could only trigger a workflow after the record was created, so we had to have a second trigger for record creation to capture values populated upon creation. I found some older posts in the forum that confirm that others experienced our past behavior too. If you've always had field entry upon creation trigger field change workflows, I wonder if it's related to our CRM environment being fairly old, and maybe MS is catching us up to modern behavior?
Business Applications communities