Option to delete MDA dropdown list items

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.

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?

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.

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.

Curious if there is any progress here? While its nice to have a way to inactivate values, its still all over the ADMIN side of the configuration and its confusing as our ownership grows. I’ve started doing that thing from the 80’s where i put ‘DO NOT USE 1’ to rename the value.

Please do something to help us keep things in order.

​@pgeorge, checking back in on this. Would a possible option here be to allow admins to move items that should be retired to a different object so they’re no longer visible? I may not have a full understanding of what it looks like on the back end, just trying to think things through.