web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Season of Giving Solutions is Here!
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / Help Needed with Custo...
Customer experience | Sales, Customer Insights,...
Answered

Help Needed with Customer Journeys in Dataverse

(3) ShareShare
ReportReport
Posted on by jseb04 45

Hi 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:

  1. A customer journey that triggers on both the creation and update of records.
  2. An existing journey that activates based on updates to the "End Date" field.
  3. 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)
  • Verified answer
    Hamza H Profile Picture
    Hamza H 1,807 on at
    To handle this:
    • Trigger the journey on record creation to start the wait.
    • Add a wait until End Date step.
    • Also, trigger the journey on updates to the End Date field.
    • Use a branch or condition to check if the End Date changed; if so, cancel or exit the current journey instance.
    • Alternatively, use Power Automate to monitor updates and cancel journeys if End Date changes, avoiding manual coding by leveraging Dataverse triggers.
    This hybrid approach ensures the journey respects End Date changes without complex data fetching.
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Season of Giving Solutions is Here!

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Pallavi Phade Profile Picture

Pallavi Phade 98

#2
Tom_Gioielli Profile Picture

Tom_Gioielli 81 Super User 2025 Season 2

#3
TAHER Mehdi Profile Picture

TAHER Mehdi 58

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans