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
Hi all -
I'm experiencing an issue with my processes that are dependent on date-specific field changes. I've noticed issues where the system will throw in any and all records into the process whenever ANY date changes are made to the record. If I build the process off of a record field change on a denial date, records without a denial date will be thrown in because another date was changed in their record... Does that make sense?
I've also found that if a process is built off of a record field change on a confirmed date, the process will trigger multiple times in a row.
I have no idea what is going on with these processes and I am out of luck at my job as no one else is able to nail down why this is happening.
Does anyone know what I can do to fix this issue?
Which process you are using?
I think you are talking about workflows in Dynamics 4.0. This is not a good solution, but you can use another field (e.g. Whole Number, Boolean) as a flag to trigger your workflow. Whenever you change your date field value, make a change to the flag too. And in the wokflow, you can check that additional field too. Again, this is not a good practice, but if your requirement is urgent you can use this as a workaround.
Business Applications communities