Option to delete MDA dropdown list items

Everything is dynamic and we should be able to delete fields in a drop-down, provided that all dependencies have been accounted for. It’s a negative experience for the end user to see something outdated and a poor admin experience to have to recreate a list of get rid of some values that are no longer needed. Please make this possible!

I have the same use case as @cankney.  We recently migrated SFDC instances, and most of the dropdown values in SFDC changed to completely different ones, so ideally, I would be able to update them to match by deleting the ones no longer in use.

If I can create it as an admin, I should be able to delete it.

Let me try to get some PM attention to this.

We cannot track if the dropdown and the dependency has already been set in the data loaded to Gainsight and hence we do not have the capability to delete. If there is data and we delete the dependency, it could corrupt the data and create inconsistent behaviour across different areas

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.

Few suggestions I have are

1. Sort the Inactive items to the bottom of the list.
2. Hide inactive items while creating new records or editing existing data.
3. Rename the item to Append “Inactive” to the item name.

Open for any other inputs. 

Thank you

Preethi

@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.

Making unwanted picklist items inactive is not the most ideal since the inactive values are still visible. Agreed with @jochle - it makes perfect sense to provide admins the option whether to make these items visible or not.

Yes Please!

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.

Can this please be prioritized?