I will also echo the need for deleting the system object from the MDA when the dynamic journey program has been deleted. Over time, retaining these with no ability to delete will make it very cumbersome to navigate the MDA in Data Management.  There really should be no need to maintain these tables once the program has been deleted.

Just revisiting this 4 months later… and the MDA is becoming VERY difficult to search and use. Programs need to be tested quite a lot, and the programs are only temporary then deleted. But the system tables created persist with zero records.

What is the long term plan for this Gainsight team?  We have 50+ test system tables since we started with the new Dynamic Programs 4 months ago. This will be hundreds within a year. 

Adding to this, we have some objects that were created based on the need at that time however, the object name is causing confusion for people that have access to Journey Orchestrator and can’t differentiate between the objects that they should be using.

@ssamarth Could we get some more info around this?

We only have one active dynamic JO right now, but I’ve created and activated a significant number of dynamic JO tests prior to the current version, and this has me a bit concerned about what the data is going to look like. @kstim, have you noticed any of this bloat in data management?

@dayn.johnson I have not! Definitely would be nice to delete the object if the subsequent JO program is deleted.