Skip to main content
New Idea

Dynamic JO - Display all participant field values in participant preview

Related products:CS Journey Orchestrator, Email & Notifications
  • August 27, 2024
  • 1 reply
  • 36 views

alizee
Forum|alt.badge.img+13
  • VIP ⭐️⭐️⭐️⭐️⭐️

Hi there

During BETA, we flagged that participant fields aren’t all loaded in the participant list if those fields aren’t used as token or otherwise mapped in the program. 

I have recently been forced to migrate our renewals program to Dynamic Programs due to a “fix” in advanced JO that broke our functional program that’d been functional for over 2 years). 

The non-sync of all participant fields is rendering participant selection quite awkward.

EXAMPLE

I haven’t mapped the relationship name to any filter, evaluate stage, email version or token and as such it doesn’t display in the participant list, which makes it extremely difficult to knock-off certain participants during review as I have to base myself solely on their email and guesswork the company or relationship they belong to. 

We need all fields to be loaded to the participant list BEFORE publishing for the purpose of reviewing the participant selection and knocking off participants. 

The workaround of working with a CSV that I would upload does sit well with me as it’s plain DIY. 

The path that took me to migrating this particular program to Dynamic was unpleasant enough, and now having to work through my participant list with a wet fingers is both daunting and concerning.

This requires a solution, soon. 

Thanks

A

1 reply

waynedilworth
Forum|alt.badge.img+4
  • Contributor ⭐️⭐️⭐️⭐️
  • May 6, 2025

Just ran into this issue for the first time - when reviewing the participant list - test records appear complete, but live records are missing key fields, as ​@alizee said - we would like to QC before publishing - but currently we have to blindly trust that the data for tokens will update.   This, coupled with the fact that we have can’t change Dynamic Program filters after publishing means my only option to test is to limit to 1 record, publish, confirm, then clone the program, remove the filter for single record, publish and QC once again.  Pretty poor experience here.  Does anyone have any better ideas?