MDA dropdown values show GSID when exported

  • 4
  • Problem
  • Updated 2 months ago
  • Solved
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.
Photo of Tom Gerth

Tom Gerth, Employee

  • 4,726 Points 4k badge 2x thumb

Posted 3 months ago

  • 4
Photo of Sarah Post

Sarah Post, Employee

  • 408 Points 250 badge 2x thumb
+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. 
Photo of Melissa Allen

Melissa Allen

  • 1,074 Points 1k badge 2x thumb
Totally agree - i had to run reports and filter on specific accounts to match up the GSIDs to the values. Bit of a pain.
Photo of Melissa Allen

Melissa Allen

  • 1,074 Points 1k badge 2x thumb
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.
Photo of Jeevan Chamarthi

Jeevan Chamarthi, Employee

  • 368 Points 250 badge 2x thumb
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.