Skip to main content
Parked

Option to delete MDA dropdown list items

Related products:CS Data Management & Integrations
  • March 18, 2021
  • 34 replies
  • 885 views

Show first post

34 replies

andybuchanan
Forum|alt.badge.img+2
  • 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.


jcyoungkin
Forum|alt.badge.img+1
  • 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
Forum|alt.badge.img+5
  • 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? 


Forum|alt.badge.img
  • 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
Forum|alt.badge.img+5
  • Expert ⭐️
  • May 13, 2025

Related: 

 


heather_hansen
Forum|alt.badge.img+15
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • August 15, 2025

I too am curious why this is still parked when there are so many votes and so many additional example use cases and potential other solutions than a complete rework.  It’s still an issue, and it’s still causing quite a bit of ugliness is reporting, rules, and dashboards.


Ravinder.Singh
  • Contributor ⭐️
  • December 17, 2025

Hi Team,

Any updates on this? We have feedback internally that having inactive values show up in the picklist creates a really poor experience for users.

Can this be looked into?


darkknight
Forum|alt.badge.img+5
  • Expert ⭐️
  • December 17, 2025

3 Years Ago:

pgeorge wrote:

Until we have a fail safe way of identifying if an item has been used, we are evaluating how we can improve the user experience for Inactive Dropdown items.

 

1 Year Ago:
pgeorge wrote:

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.

Today:
 

This continues to be one of the higher-voted issues in the community—one that affects users at every level and touches virtually every filterable feature in the product.

In this thread alone, there are examples of executive impact, admin impact, and everyday end-user impact.

@pgeorge you’ve got both strong impact and strong demand documented here. From the outside, it’s hard to understand what more is needed for this to become a real roadmap priority.

We’re consistently encouraged by Support, CSMs, and PMs to post ideas in the community, and we’re told that Product regularly reviews and prioritizes highly-voted requests. When an issue like this remains unaddressed for years despite that level of visibility, using the community starts to feel less like a feedback channel and more like a suggestion box in a hallway no one walks down anymore.

I fully understand and respect that addressing this may require significant investment on Gainsight’s side. At the same time, as a customer, my primary responsibility is to advocate for usability, data integrity, and a better experience for our users. Given the breadth and depth of the impact here, this feels less like a “nice-to-have enhancement” and more like core product debt that needs a clear plan and timeline.


ltsponhour
Forum|alt.badge.img+2
  • Contributor ⭐️⭐️⭐️⭐️
  • January 23, 2026

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.

Hello, ​@pgeorge. Has there been any movement on this? I understand that deleting is a whole can of worms. Can inactive values at least be removed from filtering lists. 

Use Case: in JO, we send different versions of emails to customers based on their pricebook. Our sales team changes the pricebook names every so often, and now we have a long list of old and new pricebook names--some of which are different by just one word--in the filter list. It would be much easier for our team if the inactive values did not show in the filters.