Skip to main content
shiv_kumar_katiyar
Gainsight Employee ⭐️⭐️
March 18, 2021
Parked

Option to delete MDA dropdown list items

Related products:CS Data Management & Integrations
  • March 18, 2021
  • 36 replies
  • 1003 views

Hi Team,

Currently, we don’t have an option to delete a particular dropdown list item from the UI. I know we can get this done from the backend in some urgent cases. It would be really nice to have a alert that gives all the dependencies for the picklist item and if there are no dependencies then allow the user to delete it?

 

Thanks

~Shiv

36 replies

alizee
VIP ⭐️⭐️⭐️⭐️⭐️
February 12, 2024

Hi @pgeorge Can we have some feedback on why the idea was parked? 

Thank you

A

The most expensive part of building is the mistakes. That's true in construction. Not so much in CSOps. So ask questions, make mistakes and learn. All views expressed here are my own.
pgeorge
Gainsight Employee ⭐️
Gainsight Employee ⭐️
February 13, 2024

Hi @alizee 

Addressing the impact of deleting a MDA Dropdown item requires significant investment on our end. Currently, this enhancement is not scheduled in our immediate roadmap and has been marked as parked.

However, we recognize that this is a highly requested improvement, and we will prioritize it as soon as we have the necessary bandwidth.

Stuart
Helper ⭐️⭐️
July 24, 2024

This remains an issue with admins looking for a solution.

 

Thanks,

 

Stuart

dayn.johnson
VIP ⭐️⭐️⭐️⭐️⭐️
July 24, 2024

This is long overdue.  Something needs to be done, even if it’s a “soft” delete that doesn’t truly delete, but can’t have these options showing up in the UI, either for filtering purpose or otherwise.

Also, I get that there may be dependencies, but if you delete a picklist value that has a filter on a rule or something like that you could build in some checks, or put in a prompt that says this will break any rule / data designer / case statement / etc. if that value is used.  An Admin should be willing / able to go through affected items and remove appropriate references and deal with ramifications if something is missed.

@pgeorge We are having the same experience as others. It seems logical for admins to be able to configure the inactive list item to be visible or not.

 

Addressing the impact of deleting a MDA Dropdown item requires significant investment on our end. Currently, this enhancement is not scheduled in our immediate roadmap and has been marked as parked.

However, we recognize that this is a highly requested improvement, and we will prioritize it as soon as we have the necessary bandwidth.

 

I understand that addressing the impact of deleting a dropdown item would require significant investment. Would a toggle to just hide inactive list items require the same investment?

The number of heavy-hitters commenting here versus the idea’s age contrast heavily with the fact that it’s been parked. Could we get an idea of what “soon” means here?

Staff CS Content & Comms Manager, 2x Gainsight CS Ops Product Council Member
dayn.johnson
VIP ⭐️⭐️⭐️⭐️⭐️
July 24, 2024

Here’s a live look at an example of the issues this problem causes:

Our “Email Communication Type” field has all the options below. There are multiple issues here.

  1. Our JO programs only sent to accounts with either the “HTML - Live Links” or the “Plain Text - Defanged Link” options, so the “Plain Text - Live Links” and “HTML - Defanged Links” options are just noise (and noise that our end users don’t understand).
  2. There is NO situation where the email communication type field should be null.

Due to both of the issues above, we have companies that are not receiving any of our JOs due to these unused fields being visible to our end users. These types of issues cause massive headaches for both admins AND end users, and seems to be a huge oversight in how these inactive options are handled.

So rather than spending a few minutes hiding options from view, we instead have to spend far more minutes tracking down and fixing the issues those visible and inaccurate options cause.

Email Communication Type Picklist

 

Staff CS Content & Comms Manager, 2x Gainsight CS Ops Product Council Member
andybuchanan
Contributor ⭐️⭐️⭐️⭐️
July 24, 2024

I second, etc this.  I’ve wanted this for a long time.  When deleting options, simply give the option of what to do with the values that are present.  Set to “NONE” or map to another picklist value same as SFDC.

Andy
jcyoungkin
Contributor ⭐️⭐️⭐️
November 26, 2024

Adding my plus-one to at least being able to hide the Inactive options.

Or use a similar functionality when deleting mappings as stated above. Allow us options for what to do with the current values, or a warning stating current values will be nulled.

darkknight
Expert ⭐️
May 9, 2025

74 votes and 4 years old.  What does it actually take to get something on the roadmap anymore?

Setting the operational impacts of this aside, how is Gainsight not embarrassed by end users/execs seeing this mess when filtering?



Also, if I add a dropdown list field to a CTA or Timeline, for example, I don’t see any of the inactive values when selecting.  I only see those inactive values when filtering in dashboard/reports.

Why can’t you just carry over the same mechanism? 

Jeff Kirkpatrick
Contributor ⭐️⭐️
May 9, 2025

I understand that deleting values opens up referential integrity problems, but it seems like making the existing “Inactive” switch hide the Inactive values from filters would be pretty low-impact and I know it would improve both the user and admin experience. 

As an anecdote, our SVP of CS (who pays the Gainsight bill) was sharing a Dashboard on a call with our C*O group and other senior leaders and was at a loss as to what the lighter-gray values were doing there in a dropdown.  Thankfully, nobody who knew the actual answer was on the call and had to share it.

If just hiding the values happens to involve lower development effort and if (as I expect) every user and admin wishes that could happen, this seems like it ought to bubble up to the top of the backlog.

darkknight
Expert ⭐️
May 13, 2025

Related: 

 

Jeff Kirkpatrick