Lance,
In cases where we are firing off some type of action that we don't want to duplicate later, we set a bit field on the appropriate record and check that as the process begins-- and exit if it's true (i.e opportunity already created).
If you use a timeout until the bid date, then if the date changes prior to the original date input, the process should adjust to it if the date field is a process trigger.
If the user wants to change the bid date after the original date and the opportunity is already generated, then I would train them to update the date on the created opportunity to the new bid date.
Mike
------------------------------
Mike Springer
Dynamics 365 Senior Consultant
PSC Group, LLC
Overland Park KS
------------------------------
Original Message:
Sent: Aug 06, 2019 10:39 AM
From: Lance Day
Subject: Cancel Existing Recursive Workflows with new Instance of Same Workflow
Hello All,
Ok, so I find myself in a situation where I will need to create an Opportunity record from a recursive workflow that is fired off when a new Project (custom entity) record is created and set to create a new Opp 7 days prior to the Bid Date that is set on the Project record. Now, that part is easy enough, but then the manager of the dept tells me there are a good bit of times where the Bid Date may very well change during the process, either to a later or earlier date. Which puts me in a position where I would need to fire off the same workflow to create an Opp, BUT also kill off the waiting workflow that was fired on record creation.
I have found this article on how to create a plug-in to accomplish this, however I am NOT a developer or have access to the tools needed to get this done (see link below). Does anyone out there know of a ready to import solution that would allow for this?
Workflow assembly to cancel waiting workflows
Thank You,
Lance
------------------------------
Lance Day
Systems Analyst, CRM
Dunbar Armored
Carlisle PA
------------------------------