MDA dropdown values show GSID when exported

@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.