Include Journey Orchestrator Dependencies in Data Management

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...

@sai_ram @lila_meyer is this an improvement we might see in the NXT instance?

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.

@sai_ram Have there been any updates to this functionality? Maybe I missed it in a recent release?

@ana_g sorry for the delay here, the discussions are still in progress. Happy New Year!!

@Cornelia and @anirbandutta I realize this is marked as ‘not planned’ but this is a really big blind spot in the product that also hasn’t been included in the new Data Management. Its absence is frankly a mystery to me - if I’m trying to determine if we can delete a field, repurpose it etc., if it doesn’t show up in the dependency checker I will STILL have to to check every single query just to make sure it isn’t in use. That doesn’t make any sense.

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!

@anirbandutta any news on this? Lack of JO dependency visibility is a huge blind spot. Not only does every query need to be checked, but each field in a transform step, each custom mapped field, each template token, each conditional wait, email template variation, etc. Even if you have one program that’s quite a bit to validate, and the time component only multiples from there as you have more than one program.