Skip to main content
  • Home
  • Ideas
  • Allow updating values on picklists when disabled value is active

In the realm of data’s grand domain, A challenge rises, causing strain. Multi picklist fields, once so bright, Now shrouded in a shadowed plight.

Disabled values, locked in place, No manual touch, no rule’s embrace. Engineering’s decree, support’s refrain, “Expected behavior,” they maintain.

Yet once, in days of yore, it seems, We could update, fulfill our dreams. Now hindered by this puzzling stance, Our data’s growth, it can’t advance.

To remove the old, to bring the new, This simple task, we can’t pursue. A call to arms, for sense to reign, To free our records from this chain.

Oh, let the fields be free once more, To update, change, and to explore. For in this epic data quest, We strive to make our systems best.

 

In short, we can’t update records where a disabled value is selected in a multi-select picklist field. Engineering and support claim it’s expected.

It doesn’t seem to make any sense to prevent the removal of said value, and to prevent the update of the record with new updated values, making these records locked forever until we re-enable values to make a batch CSV upload to correct the problem… 

Thanks! 

A

Wait - so any record that has a multi-picklist field on it, where one or more of the values in that field are inactive, the *entire record* cannot be updated at all?

Or does this mean that trying to update just the multi-picklist field on that record doesn’t work, if one of the values for a given record is inactive?

@bradley Sad but true… you cannot update the picklist field at all - however the ripple effect on a rule that updates more than one field… including the multi picklist in question could be bad. 

Here’s support’s answer: 

We have received feedback from the engineering team and would like to inform you that disabling inactive picklist items is standard behavior across most areas of Gainsight. If an item that was previously active and selected is marked as inactive, it becomes disabled and cannot be selected or deselected in the dropdown.
 
Currently, there is no built-in approach to handle this, and no platform features are available to allow users to find the dependencies of a picklist item before marking it inactive.
 
The only current solution is to make the item active again, adjust the data in the People tab, and then mark it inactive once more. This is the only way to avoid errors when making new selections for picklist items, and there are no immediate plans to change this on the roadmap.*

 

You cannot edit them at all, including not select an additional value that is active. 

@alizee Gotcha, but you can edit other elements on the records though? Both seem like bugs for sure, but not being able to edit a record in any way either would seem to be a much bigger problem as well.

Terms & ConditionsCookie settings