[Feature Request]Increase Functionality for Setting & Clearing Multi-select Picklist

  • 5
  • Problem
  • Updated 7 months ago
  • Acknowledged
Once upon a time a there was a community concerning writing into Mutli-Select Picklist 2 years ago and its still in progress.

There are quite a few customers that have talked about using the multi-select picklist, but was stopped short by it's limited behavior. It gets treated like a single value picklist when any rules attempt to set it.

Also, you are unable to clear or append to it properly.

A use case here, a customer has multiple line items of enabled products, I would like to set the Multi Picklist to say that this customer has these products enabled. Also once one product goes inactive I would like to refresh it with current multi select values. Rules doesn't handle this use case really well with current multi-picklist functionality.

Sure you can use checkboxes, but it gets really messy and not in a neat package. Also Customer tags can't be deleted once added via rules.
Photo of Kevin Ly

Kevin Ly, Employee

  • 3,268 Points 3k badge 2x thumb

Posted 1 year ago

  • 5
Photo of Sundar

Sundar, Alum

  • 11,370 Points 10k badge 2x thumb
Less interesting fact - The behavior of append and remove few items from the list, remove all the items within a single field requires a full revamp of our field mapper. I understand that this is crucial for utilizing the multi-select effectively. 

With our addition of the MDA multi-select dropdown, we should be taking up with higher priority. Thanks for bringing this up.
Photo of Kevin Ly

Kevin Ly, Employee

  • 3,268 Points 3k badge 2x thumb
Hmm, Maybe we can stick with a custom mapping only for now where we can reset the entire picklist and one to set one. The source mapping to multi picklist prob won't be needed as the filter criteria can improvise. With this suggestion, we don't need to revamp the mapper, just the custom mapping ability for multi select picklist where I can check a box to append or to reset the entire list.
Photo of Lucas Schuelter

Lucas Schuelter

  • 116 Points 100 badge 2x thumb
Currently this is causing a very big problem to us. We want to create a rule to only add a tag to some customers, but we can't do that - once if we map a rule to update a field with a tag, it erases all the tags that were added before.

For us, this is an urgent interface/UX issue. We noticed that after months of operation and actually we don't know how big is the impact to us. A lot of organizations may be affected by this issue and did not notice that.

The multi-select picklist fileds at the rule setup should have a functionality to select if the rule should:
1) reset the field and then select some values;
2) maintain the previously selected values and add a new value.
Photo of Heather Hansen

Heather Hansen, Champion

  • 9,224 Points 5k badge 2x thumb
We have this same use case.  Luckily, the tag it replaced was only for a few accounts, so it wasn't too big a pain to add it back manually, but as we look to use Tags for more items, this is going to be a significant problem for us.