Skip to main content
New Idea

Add The Ability to Pull Salesforce Picklist Label

Related products:None
  • February 23, 2022
  • 2 replies
  • 98 views

jordan_cook
  • Contributor ⭐️⭐️⭐️⭐️
  • 46 replies

The problem:
Many picklists in our instance of Salesforce have a difference between the value and the label.
For example, the value for Account.Type may be something like 12860112, while the label for that value is “Customer”.

This causes us problems when creating Bionic rules that query objects in Salesforce that have picklists like this. Instead of getting the friendly label “Customer”, we get the numeric representation of this value, which is not helpful when mapping to a picklist in Gainsight. We have to create super long custom mappings in our rule actions in order to even sync this data. 

Example:
This pseudocode below further illustrates my issue.
When I execute the SOQL query in Salesforce like this:

SELECT Type FROM Account
LIMIT 1;

I get the result: 12860112

But when I execute the query here:

SELECT toLabel(Type) FROM Account
LIMIT 1;

I get the result: Customer

The request:
Throughout Gainsight (rules engine, connector sync jobs, data designer, etc) give us the ability to apply the “toLabel” function (as outlined above) to any given field with a picklist data type. This would allow us to retrieve the friendly value that users actually see in Salesforce, and allow us to auto-map the field in Gainsight.

2 replies

jordan_cook
Forum|alt.badge.img+2
  • Author
  • Contributor ⭐️⭐️⭐️⭐️
  • 46 replies
  • September 21, 2023

Just getting burned by this one again today. We are really having to jump through so many hoops to accommodate the changes that are being made in Salesforce. When the Salesforce teams adds or removes items from a picklist, we essentially have to manually update Gainsight picklist to match - there is no way to automate this that we can find.


bradley
Forum|alt.badge.img+7
  • Expert ⭐️
  • 1130 replies
  • September 21, 2023

Yea I actually have a ticket open related to this 270267 (for any Gainster watching), where in our case the SFDC label is completely blank and they’re looking at pulling the value instead.

Doesn’t seem like they’ll just grab value instead all of the time, but label vs value is still the problem. 

To your point, sometimes we may actually want one vs the other as something we can select, which would have solved our problem here as well most likely.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings