Ability to Delete System Object/Have option to Delete System Object that is created when JO/Dynamics Programs are Published and Program is Deleted

THIS. This right here. ☝

Feels like the same should be true for DDs, etc.

Or have a properly documented “object source” field so we can differentiate between JOs, DDs and Surveys (although those have a suffix appended). 

thank you ​@alizee ​@dayn.johnson. This was created to provide a separate placeholder for the program and participant custom field data, outside of the AO Participants object.

As an immediate measure, please submit a support ticket with the list of objects you want to delete, and we will handle the deletion for you. ​ ​@mgamache ​@jrich 

For a long-term solution, I am discussing with the team ways to better classify these objects and simplify the structure to reduce clutter. We are also considering implementing a feature to delete the objects when the associated program is deleted.

​@vmallya Thank you for the clarification! This makes sense, and it’s fantastic to be able to have that data accessible. Like ​@alizee suggested below, if these had a clean object source classification, I think having these extra fields does more help than harm. It’d massively simplify reporting and dashboard creation to be able to pull participant data from these individual objects without having to track down the specific AO program ID to filter on.

As long as the dependencies were clear as far as deleting active JOs that were using these objects, that might also be a good way to prevent the accidental deletion of important, ongoing programs. 🤔

Hi, I second this request, due to the heavy usage of JO we do and the plethora of test JOs (now deleted) that pollute the MDA. Having the ability to delete them once the Program is deleted would be great!

There is no need to keep the system object associated with a JO if the JO itself is deleted.

This is very needed, and could perhaps be set up similar to how Data Designs and their associated system objects are handled when deleted. I believe that currently when a Data Design is deleted, the associated system object is also deleted in tandem (assuming there are no dependencies lingering). This would help with maintaining a clean Gainsight instance.

Thinking things through here, are the system objects associated with the new dynamic JOs tied to the AO objects for JO reporting needs (or for use in other JO logic)? If so, I can understand that reasoning for why those system objects aren’t deleted.