Skip to main content
New Idea

Allow Admins to Disable Linked Object Record Deletion

Related products:CS Cockpit & Playbooks
  • September 2, 2022
  • 7 replies
  • 114 views

bradley
Forum|alt.badge.img+9

I saw this post, requesting that deleting a CTA not delete the associated linked object(s) but I think this request is different enough that it deserves its own post. At the very least, it has not been implemented even if there is overlap.

 

Here is a use case/context around this:

 

  • You have a low volume custom MDA table that you have configured as a linked object to a Lifecycle or Objective CTA for example. 
  • On a C360 report, users can add or modify records to the table but they can not delete them.
  • As a linked object on a CTA, users have the following actions however:
    • Create New record
    • Associate Existing record to the CTA (and then modify it)
    • De-Link the Associated Low volume Record
    • DELETE the associated Low Volume Record

The last option actually deletes the record out of the object and is visible in data management:

 

This opens the possibilities for end-users to completely remove a record from an object whether they intended to do that or not. While a confirmation dialogue box does come up, the de-link vs delete distinction is not one all end-users will always action on appropriately. At best, deleting a record in this way only negatively impacts the single user. At worse, it could cause major downstream problems.

 

Please give admins the option to disable the ability to delete these records as a permission, part of the linked object configuration or something. As it is, this presents a blocker for us in adopting this feature.

 

7 replies

Forum|alt.badge.img+2
  • Contributor ⭐️⭐️
  • November 25, 2024

Has this been reviewed by Product team to determine its feasibility and if it is possible to add to roadmap? 


bradley
Forum|alt.badge.img+9
  • Author
  • Expert ⭐️
  • December 2, 2024

@revathimenon 👀?


revathimenon
Forum|alt.badge.img+8
  • Gainsight Community Manager
  • December 3, 2024

I’ve raised this internally with the team, ​@bradley 


Forum|alt.badge.img
  • Contributor ⭐️⭐️
  • October 6, 2025

@revathimenon any updates on this? It’s preventing us from utilizing this feature


revathimenon
Forum|alt.badge.img+8
  • Gainsight Community Manager
  • October 8, 2025

@jaymeb let me raise this internally and see what I can find. 


Forum|alt.badge.img
  • Contributor ⭐️⭐️
  • October 29, 2025

Hey ​@revathimenon, any updates? 


andybuchanan
Forum|alt.badge.img+2
  • Contributor ⭐️⭐️⭐️⭐️
  • February 20, 2026

to pile on here this should be something that should be configurable.  If we are ingesting data from an external source, really not a good practice to add or delete records.  Where we simply want to display data, and maybe have them update a field or two on the record should not empower them to delete a record or create a new one.  I can see why this would be needed, but not in all situations.