Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
Howdy,
Been testing out BigQuery with PowerBI and found that if we set a field to DATE and not TIMESTAMP. PowerBI still attempts a TIMESTAMP conversion which throws the follow error.
Now we can work around this with TIMESTAMP. But support for DATE would be nice, and thought I could provide feedback on the Beta Connector.
Cheers,
Ken
Solved! Go to Solution.
Hi @Ezi_Ken,
I have gotten the response from the Product Team. The fix will be available in January 2018.
Best Regards,
Dale
Hi @Ezi_Ken,
I have reported this issue to Product Team internally: CRI 52692290. I will post the updates in time.
Best Regards,
Dale
Hi Dale @v-jiascu-msft,
Thanks for the fast feedback. More context, I am doing direct query straight to a BigQuery dataset (not a SQL query). Which it comes back fine. Issue is when I attempt to put the date field into a visual such as a matrix or table... Then it throws that error which I saw.
Cheers,
Ken
Hi @Ezi_Ken,
I have gotten the response from the Product Team. The fix will be available in January 2018.
Best Regards,
Dale
It appears this is still not fixed? Can anyone confirm and, if so, offer a workaround solution?
Hi @Ezi_Ken,
It seems that the limits are from the legacy SQL of BigQuery, which has limit support for Date type. Maybe you should use standard SQL in BigQuery. It works fine in my test.
You can see the details in my test.
Reference: https://cloud.google.com/bigquery/data-types
https://cloud.google.com/bigquery/docs/reference/standard-sql/enabling-standard-sql
Best Regards,
Dale
User | Count |
---|---|
98 | |
90 | |
78 | |
71 | |
64 |
User | Count |
---|---|
112 | |
96 | |
95 | |
67 | |
65 |