Extract Data connector does not retain underlying data's data types. [377948394]

Assigned

Bug

Status Update

No update yet.

Description

sa...@yamaretto.com

created issue #1

Nov 7, 2024 08:56PM

For example, an underlying data set has currency values, but upon extract, these become numbers.

Each time we save and extract the data, the values revert to a "Number" type rather than a "Currency" type.

This creates an unnecessary amount of extra work to adjust the metric type to the correct type.

Comments

pu...@google.com <pu...@google.com> Nov 8, 2024 06:36AM

Assigned to ar...@google.com.

ar...@google.com <ar...@google.com> #2Nov 8, 2024 10:56AM

CORRECTION: this is only pertaining to Scorecards, I'm aware I can do this on a table. My apologies.

sa...@yamaretto.com <sa...@yamaretto.com> #3Nov 8, 2024 07:57PM

@ar..@google.com

Please see the attached screenshots.

I'd expect the Type in the Extract to be the same as the Google Sheet from which the data is extracted. I can change the Type in the extract to currency manually, but if I go back to re-extract the data, the Type reverts to a Number.

Steps to reproduce: Take a Google Sheet data source with a metric with a type of "Currency", extract the data, look at the type the metric is in the extracted data source.

Message last modified on Nov 8, 2024 07:58PM

Screenshot 2024-11-08 at 11.36.32 AM.png

112 KB

View

Download

Screenshot 2024-11-08 at 11.32.59 AM.png

84 KB

View

Download

ar...@google.com <ar...@google.com> #4Nov 11, 2024 11:49AM

Hello,

Can you please confirm if you have a subscription to Looker Studio Pro?

ep...@gmail.com <ep...@gmail.com> #5Nov 11, 2024 06:42PM

Same problem with geographic data of latitude and longitude.

sa...@yamaretto.com <sa...@yamaretto.com> #6Nov 11, 2024 06:47PM

I do not have a subscription to Looker Studio Pro -- does this feature work in Looker Studio Pro?

ar...@google.com <ar...@google.com> #7Nov 13, 2024 06:22AM

Hello,

Thank you for reporting the issue.

This issue report has been forwarded to the Cloud Looker Studio Engineering team so that they may investigate it, but there is no ETA for a resolution. Future updates regarding this issue will be provided here.