Customer experience | Sales, Customer Insights,...

Real-time Marketing: Per-record reminders when logic is on a child table

(4) Share

Report

Posted on by jseb04

Hi everyone,

I’m looking for advice on the best architecture in Dynamics 365 Real-time Marketing for reminders that must be sent per record in a custom Dataverse child table, while segments/journeys are Contact-based.

Scenario (generic)

Standard table: Contact
Custom child table: Application (many-to-one from Application → Contact)
- A Contact can have multiple Application row
Each Application row contains:
- StatusCode (examples: Accepted, ConditionalAccepted, Confirmed, Cancelled)
- DecisionDeadline (date)
- EarlyReminderSent (Yes/No) + EarlyReminderSentOn (datetime)
- FinalReminderSent (Yes/No) + FinalReminderSentOn (datetime)

Requirement

Send two reminders:
1. Early reminder sometime before the deadline (e.g., next month / within N days)
2. Final reminder ~7 days before the deadlin
This must be done per Application row (not per contact), because a contact may have multiple concurrent applications and each one must be tracked independently (flags stored on Application).

Constraint

Real-time Marketing segments can only target Contact/Lead, not the custom Application table.
Therefore, a segment-based journey runs at the Contact level.
But the decision/flags are at the Application level.

Approaches I’m considering

Option A — Contact-based segments/journeys + Power Automate resolves child rows

Contact segment identifies contacts who have at least one eligible Application
Journey sends reminder email
Journey calls a custom trigger passing Contact context
Power Automate:
- queries eligible Application rows for the contact
- updates flags on the correct row(s)
Concern: If multiple Application rows are eligible, the journey email content may be ambiguous unless the flow determines the “right” row, or sends multiple emails.

Option B — Power Automate drives per-Application runs + trigger-based journeys

Scheduled Power Automate queries the Application table for eligible rows
For each eligible Application row, Power Automate triggers a custom-trigger journey, passing:
- ApplicationId
- Contact reference
- optionally DecisionDeadline / ProgramName for personalizatio
Journey sends email and then triggers another action/flow to mark that specific Application row as “sent”
More moving parts, but fully per-record accurate.

Question

What is the recommended / supported best practice to ensure reminders are per child record, given that segments/journeys are Contact-only?

Keep journeys contact-based and resolve child records in Power Automate?
Or let Power Automate be the driver and use trigger-based journeys per child record?

Any guidance or patterns from real implementations would be appreciated.

Thanks!

Categories:

Dynamics 365 Customer Insights - Data

Outbound to Real-Time Transition

Microsoft Dynamics CRM

Dynamics 365 Customer Insights - Journeys

All responses (4)

Answers (0)

Sort by

Shivani Padalia 40 on at

Like (2)

Report
Copy link

Link copied!

In real implementations, Option B (Power Automate drives per-Application runs + trigger-based journeys) is cleaner and more reliable pattern.
TAHER_El_Mehdi 1,984 on at

Like (1)

Report
Copy link

Link copied!
Best Practice for Per-Record Reminders in Real-time Marketing

Option A — Contact-based Journeys + Power Automate

Segment identifies Contacts with at least one eligible Application.

Journey sends email and triggers Power Automate to update Application flags.

Limitation: If multiple Applications are eligible, personalization becomes ambiguous. Works only if a single email per Contact is acceptable.

Option B — Power Automate + Trigger-Based Journeys (Recommended)

Scheduled Power Automate queries Application table for eligible rows.

For each Application row:

Trigger a custom event in Real-time Marketing with ApplicationId, ContactId, and personalization fields.

Journey sends a personalized email for that specific Application.

Update flags (EarlyReminderSent, FinalReminderSent) after sending

Benefits: Accurate per-record reminders, clear personalization, scalable, and compliant.

The Bottom line:
If reminders must be specific to each Application, use Power Automate to drive per-record triggers and start custom-event journeys. Contact-based journeys are only suitable for generalized messages.
Suggested answer

rajeshjamrodh 62 on at

Like (0)

Report
Copy link

Link copied!

Hi @jseb04
In real time marketing we have created different -2 campaign and target the specific customer as per segments based.
Yes. In Dynamics 365 Customer Insights – Journeys (Real-time Marketing), a common requirement is:
Send a reminder for each Contact based on a date/condition stored on a child/related table.
The key challenge is that the journey trigger and audience context must be designed around the table that actually contains the business event/date.
Example
Suppose you have:
Contact
│
│ 1:N
▼
Loan Application
│
├── Application Number
├── Application Status
├── Due Date
└── Reminder Date
Business requirement:
For every loan application, send the associated contact a reminder as per your campaign is created days before the Reminder Date again trigger the particular customer, But when customer is not open the received email campaign.
Suggested answer

Syed Aqib Raza 138 on at

Like (0)

Report
Copy link

Link copied!

Option B — Power Automate drives everything ⭐ Recommended pattern

Join the conversation

Community site session details