We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
Hi,
My PowerBI report that connected to Dateverse via directly query had been working perfectly until Saturday 25/2/23.
I have been getting below error message.
When I take a closer look into the table, the decimal number wasn't picked up correctly through dataverse table.
For instance, when i create a custom column with number 1982.33 but the column value turn out to be some weird number of 1.98233e+003. I am wondering if this is a bug on the update version?
Any idea on how to fix this would be greatly appreciated.
Thank you
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 5 | |
| 3 | |
| 3 | |
| 2 | |
| 2 |
| User | Count |
|---|---|
| 10 | |
| 8 | |
| 7 | |
| 7 | |
| 5 |