Hi @tom_gerth  - did you by chance get a status on this?

We’re encountering this issue with JO right now when trying to query and we’re getting data that people don’t understand as a result.

thanks,

I created a report with some Picklist fields and did export. It’s showing the Names names only, I didn’t see any ID’s are displaying instead of actual text values.

Thanks.

Any resolution on this.  We just set up an S3 export for our data team and all the picklist data came through as GSIDs. 

I too have the same issue, we are trying to export data to S3 and all the picklist data came through as GSIDs. 

@Nalin and @Justin Bills  acknowledged your request. I am checking on it. 

As an update - I did open a ticket on this.  It was something that was fixed with flipping something on the backend.  I’m not entirely sure if that opens all up all pick list fields to show the value instead of the ID, or just the one I was writing in about. 

I see multiple product areas being discussed here: 

1. Reporting → When you export a report which has a dropdown value we are currently showing labels only, not GSID’s. If anyone is getting GSID’s in any scenarios, I recommend raising a ticket.
2. Rules S3 export → We have a backend flag which when changed will also send the label in addition to the GSID. This should be on for newer customers by default, for our older customers who might have already created some data flows using GSID’s we could not automatically do this change for all customers. Please reach out to support if you want this for your org

Hope this covers everything

@Nalin and @Justin Bills did you get a chance to see the comments here?

@sai_ram : Yes, I did check the comments. I have raised a support case for this issue.

This is a pretty major issue in my opinion. I see that I can ask support for including the name too, which I will do. But the issue still remains that we can’t use MDA picklists in string formulas at all in the Rules Engine - i.e. you can’t do a LEFT formula, you can’t convert them as a string using Case Expressions, etc.

This is especially frustrating considering you can do all of the above with SFDC picklists. Why would our MDA picklists not function the same way?

Yessss! Agree with all of the above comments. This and BOOLEAN field limitations have been super frustrating for me recently.

Here’s another scenario where storing the picklist values as GSIDs leads to frustration 

@rakesh The ability to leverage the actual Picklist values throughout GS is becoming more crucial.  I just added this question in another post.

Came across this issue just yesterday and had to push to a new object string field just to work with it.

@Wayne yes that’s an option, though I really don’t want to create a duplicate field just to work around this issue.

Agreed, was adding on to the annoyance and extra work/resources that is needed to work with this lack of a feature. 

Adding to the chorus of voices here, the ability to export picklist values as they are labeled quickly and at scale (without workarounds of extra tables, fields, rules to manipulate extra tables/fields, CASE statements, etc.) would be a big win.

How do transition this need beyond a “Question” thread to become an idea we can upvote?

@matthew_lind  - is this still an issue for you ? 

@Azad   in a larger sense, yes.  This isn’t just about getting the extra field in an export.  It’s about the bigger picture.

• This caused our Snowflake team to do some hefty data management acrobatics on import because the native picklist/multipicklist field only exports the GSID.  
• This prevents us from being able to leverage the data in external API action in various ways because the field natively only exports the GSID.
• This prevents us from being able to do field comparisons (i.e. between Salesforce and GS) because one side natively contains a GSID, without making custom case expression fields that limit you to 10 cases.
• This makes it very difficult to use Rule/Program execution logs.

The workaround where Gainsight exports an extra field containing the label should be considered a workaround only.  When would an admin ever use the GSID value of a picklist/multipicklist field over the label (especially when we have no way of looking up the GSID of each value)?

This has become a bigger issue for us in NXT where admins have greater ability to create custom fields and so this issue will only grow, not diminish.  Admins should not be required to contortion complex and costly solutions to work around such a gap. 

@heather_hansen @bradley @brad_tippetts @mindym @mindy @travis_floyd