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.
Include Journey Orchestrator Dependencies in Data Management
None
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
I have also noticed this being a weak spot in JO migrations using Query Builder for the Participant Sources. I have had to rebuild Journeys too often...
Hi Ana, there are some dependency warnings related to JO in data management. More info here. If this isn’t quite what you’re looking for, can you explain a bit more?
Hi@lila_meyer this is the Data Operations feature, but I am referring to MDA object dependencies, specifically for Custom objects. There is a section for Email Templates but not for the actual queries.
Can someone help me understand why this has not been, and apparently will not be, addressed?
Let me try to get some answers here@bradley
Resurfacing -- just hitting this issue now. We have over 70 journey orchestrator programs, accounting for over 100 email templates. This makes our lives quite difficult when we have to assess impact of field changes!
Let me try to get some answers here@bradley
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
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.
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???
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.