Skip to main content
Helper ⭐️
May 7, 2020
New Idea

Include Journey Orchestrator Dependencies in Data Management

  • May 7, 2020
  • 16 replies
  • 249 views

We’re doing a little spring cleaning and I noticed that there is no dependency section for objects used in JO programs (unless I am mistaken?) This is a huge blind spot and can lead to email programs not working if data is inadvertently deleted before the program is rebuilt to use a different MDA object. 

16 replies

anirbandutta
Expert ⭐️
July 21, 2022

@PavanCh could you pl share the latest on this usecase?

It's an opportunity for engagement
PavanCh
Gainsight Employee ⭐️
Gainsight Employee ⭐️
August 2, 2022
Updated idea statusNot Planned→Under Consideration
PavanCh
Gainsight Employee ⭐️
Gainsight Employee ⭐️
August 2, 2022

Happy to share that we are actively considering token dependencies management as part of the Journey orchestrator redesign project. The first build is expected to be beta ready H1, 23

bradley
Expert ⭐️
August 2, 2022

Happy to share that we are actively considering token dependencies management as part of the Journey orchestrator redesign project. The first build is expected to be beta ready H1, 23

Great news! Will the fields used in the queries be a part of that as well? Being able to track query level dependencies just like we can with rules would be the biggest gain for admins.

bradley
Expert ⭐️
August 3, 2022

@PavanCh @anirbandutta @GameChangerAdmin 

This was marked as ‘not planned’ up until a day ago. Today I discover this in dependencies:

 

So does this mean that this idea has been implemented? Or implemented for some objects? Or for queries but not for tokens???

Contributor ⭐️
November 22, 2022

@PavanCh 
Looks like its limited to MDA, can we also include Salesforce objects?
There is no way to know dependency fields for SFDC objects used in JO programs 
 

fyi, working with support on this (ticket  #205508); any interim solution would be appreciated.