Skip to main content
tom_gerth
Gainsight Employee ⭐️⭐️
August 1, 2018
Question

MDA dropdown values show GSID when exported

  • August 1, 2018
  • 41 replies
  • 1326 views
We've noticed that when including an MDA dropdown list field in a report, we get the GSID values when we export said report, versus the value's display name.

We show the display name in the report itself, but as soon as it's exported, we get the GSID that we are unable to decode and understand the text value.

41 replies

sarah_post
Helper ⭐️
August 1, 2018
+1 to this.  I've been looking for a solution to this problem when exporting to S3 via Bionic rule - only the GSIDs for MDA dropdown values are exported, not the actual value. (Same if you transform the data in any way - still only GSIDs are exported.)  Also the GSID isn't displayed in the Category (dropdown) UI so you have no way to marry the values to the correct account fields post-export. 
melissa_allen
Contributor ⭐️⭐️⭐️
August 1, 2018
Yes - this is definitely an issue. I found a lot of issues in copilot when i go to use one of the dropdown fields as a filter, and have to figure out the GSID code instead of using the text value. For example, instead of filtering on something like "Mid-Market" i have to filter on the full code: 1I0054U9FAKXZ0H26HUNX1G915T5I65JS9C4. While this is a pain, the reports are more of an issue. In the report, the field display's correctly in the view, but when you export it out, it has the GSIDs in the export file, which is extremely confusing for users. 

It would seem that if we can use the dropdown lists to filter reports, we should be able to export it out with the text values and also use it to filter in copilot.

My current workaround is to also make a text field that i map the values to, but that means i have to create 2 fields for each field i want to create a dropdown field for. That is a lot of extra work and is confusing if you have other users creating reports that might not know to use the nondropdown fields for the visual portion of the report.
melissa_allen
Contributor ⭐️⭐️⭐️
August 1, 2018
Totally agree - i had to run reports and filter on specific accounts to match up the GSIDs to the values. Bit of a pain.
jeevan_chamarthi
Contributor ⭐️⭐️⭐️
August 4, 2018
Thanks Tom for bringing this up. We are working on a fix, will be able to update this thread as soon as the fix is pushed to production.
prithvi_vihari
Helper ⭐️
September 6, 2019
Hey Jeevan- Just came across a customer for whom the export from report builder still shows GSID's rather than the value/label of the dropdown list. Could you confirm this fix is still active?

tom_gerth
tom_gerthAuthor
Gainsight Employee ⭐️⭐️
September 17, 2019
Hey @jeevan_chamarthi ,

Do you know what the status is here? I know this is set to solved but this has been reported to me multiple times in the last few days.

Enterprise Support Manager, Gainsight
cnichols
Helper ⭐️
November 2, 2020

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,

 

 

phani_kumar
Gainsight Employee ⭐️⭐️
November 2, 2020

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.

Justin Bills
Helper ⭐️
December 9, 2020

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

Contributor ⭐️⭐️⭐️
December 23, 2020

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