Skip to main content
New Idea

Avoid remapping fields in versions/filters when updating Data Design source in Dynamic JO

Related products:CS Journey Orchestrator, Email & Notifications

alizee
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • 655 replies

Hi all,

I’m working on the transition of one of our programs to Dynamic JO while at the same time reworking the program’s reach / capabilities with the new features.

Since at the date of posting, query builder isn’t back, I’m using data designer as a source and I’ve noticed that whenever I modify my data designer (because I face difficulties with some aspects of calculated fields) to add new fields (i.e. I converted my multi-select picklist “Roles” into a boolean as multi-select isn’t supported in calculated fields), Dynamic JO doesn’t notice / pick up the new fields I’ve added to the design. 

I have to delete the source, and re-add it for the fields to be picked up and available as tokens or filters in email versions. Even re-syncing the source doesn’t do the trick. The fields don’t show up automatically, which is causing several problems: 

  1. All the pre-sets evaluate stages and calculated fields have to be updated
  2. All tokens in emails have to be updated
  3. All filters for email versions have to be updated

This is quite a big waste of time when the design changes are to make up for the issue with multi-select picklists. Even in cases where it’s to accommodate something one’s forgotten as a field of importance, it creates a lot of extra work.

I believe the change in behavior is also because we’re no longer mapping fields like we did in Advanced JO, but I believe a bit of an improvement is necessary here (even if it’s not necessary so straight forward). 

I’d like to make sure that fields available in the data design appear as you add them to the data design / space, provided said design has been re-run in DD. 

This would save a ton of time. 

Thanks!

A

7 replies

zach_davis
Forum|alt.badge.img+3
  • Helper ⭐️
  • 77 replies
  • January 22, 2024

+10000


alizee
Forum|alt.badge.img+11
  • Author
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • 655 replies
  • January 23, 2024

Update: I am now in the process of remapping the values, and it turns out that my Participant Field (Region), which is a single select picklist, doesn’t have any of the picklist values loading when trying to remap them. Meaning I have to completely remove my evaluate stage and rebuild it completely, which adds to the time required whenever you’re adding fields.

 


alizee
Forum|alt.badge.img+11
  • Author
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • 655 replies
  • January 24, 2024

I’ll add one clarification point after further testing this morning: 

  1. The new fields show up when clicking on Source Fields > View
  1. They do not anywhere else in evaluate stages and email versions, which is where the need to remove the source and re-add it and then remap comes in

alizee
Forum|alt.badge.img+11
  • Author
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • 655 replies
  • January 24, 2024

@vmallya CC’ing you for visibility as this caching issue resolution would really, really change things for us JO builders. Thank you!


vmallya
Forum|alt.badge.img
  • Gainsight Employee ⭐️
  • 48 replies
  • January 25, 2024

@alizee - we have identified this and fixed the experience. when new fields are added in sources, they will be updated and available in JO programs (once the program page is refreshed) and those fields can be used for tokens or any conditions/filters. This should be available on or before feb 10th. 

Thanks for the callout 👍🏻


alizee
Forum|alt.badge.img+11
  • Author
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • 655 replies
  • January 25, 2024

@vmallya Excellent, that’s great news and I can’t wait for it.


corey.henningsen
Forum|alt.badge.img+3

Hello @vmallya , I wanted to follow up to see if this has been fixed. Thanks!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings