Skip to main content

Use case:
We are working on a rule where one of the picklists grew a lot, and we have ~200 new values to add. The first issue is that you can’t export the existing 150 to validate which ones already exist in the dropdown. If the value exists in the dropdown but not in the object, we can’t identify them via rules engine.
Related idea: 

 
Some manual effort combined with some workarounds, and we were able to update the dropdown list… So we got to issue #2: It did not update the mapping in the rule, we had to manually map all the missing values to maintain all the actions in one branch (I didn’t get a screenshot from the Horizon rule, so I’m using an old bionic one with the same field as an example, but the behaviour was the same in both)

The funny thing is that it will default correctly if creating a new branch in that same Horizon rule… So, can you please replicate this behaviour?

 

 

We need a post recapping all the issues with picklists so it can be looked at as one product that is in serious need of fixing.


@rakesh There is so much that isn’t ok with picklist (and multi-select especially) - would it be possible to have a VCAM about it at some point? 


Hi @romihache, thank you for sharing the feedback here.

For issue #1: I do see the new picklist values are reflected in the Horizon Rule (please refer the screenshot).

For issue #2: I will share this with my team for evaluating the most suitable solution for this use case and get back to you.
 

@alizee Sure will plan a VCAM around it.

 

 


Hi, Sorry for the confusion @shambhawi.
For issue #1 I meant to identify them in bulk (for example, downloading all the items from the dropdown to a file and doing a vlookup), not one by one. In the example above, it would be easier and quicker to identify the ~50 missing values, and import them via CSV than scrolling through the list within the rule, and adding them manually.


Sorry @shambhawi,
I also should add that I was also working with an external list that I wanted to compare with the existing dropdown values in Gainsight to add all possible values in one go, and not only the ones in use at that particular moment to avoid missing mapped values in the future.