[Feature Request]Increase Functionality for Setting & Clearing Multi-select Picklist
None
Once upon a time a there was a community concerning writing into Mutli-Select Picklist 2 years ago and its still in progress.
https://community.gainsight.com/gainsight/topics/writing-to-multi-select-picklist-in-rules-engine-ta...
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.
https://community.gainsight.com/gainsight/topics/writing-to-multi-select-picklist-in-rules-engine-ta...
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.
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
With our addition of the MDA multi-select dropdown, we should be taking up with higher priority. Thanks for bringing this up.
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.
Also it looks like the post linked to Kevin's entry is gone.
I was actually able to work around this and successfully set multiple tags with the rules engine. It’s possible with bionic rules so long as you can build up to a single data set that will allow you to set all the tags at once.
The multi-select tag field is basically a semicolon-delimited string. So I created a data set with the account ID, and then a boolean for each tag. Then I did a transform task and used the case statement. If the boolean is true I set the string output to “TAG STRING” followed by the semicolon. If it was false (because you have to put something in the field) I just put the semicolon. In my task I had 3 case statements.
Then I did another transform task and used the Concat function to just put them all together. So I have a string that says “Tag A;Tag B;Tag C;” or “Tag A;;TagC” or even “;;TagC;”. Update Customer under actions and use that string to set the Tag field. Salesforce just ignores the extra semicolons.
Are there any updates on this front (besides multi step workarounds in Rules Engine)? This would be much needed in my org!
as the idea apparently is 6 years old???
any updates?