Share
Report
45Hi everyone,
I’m looking for guidance on creating a customer journey in Dataverse that triggers when a new record is created in a table. I want the journey to wait until the "End Date" and then cancel if that field changes before reaching that date. I also need to consider scenarios where a script might change the "End Date," making the current customer journey no longer valid.
Here are a few options I'm considering:
- A customer journey that triggers on both the creation and update of records.
- An existing journey that activates based on updates to the "End Date" field.
- Using Power Automate with a daily schedule to check conditions: if today matches the "End Date," it should trigger a customer journey and perform an unbound action (though this seems like a lot of coding to fetch all the data).
Has anyone dealt with a similar scenario? Any tips on structuring the journey, particularly regarding the wait condition and handling updates to the "End Date," would be greatly appreciated!
Thank you in advance for your help!
I have the same question (0)
All responses (
Answers (
