Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
Data View
Table, all dollars are currency and summarized
Data is accurate in Query too.
Other details: If I refresh on my desktop using ODBC connector, then all the data displays. I can then publish it and the data will show online. Once an auto refresh occurs online using the gateway connector the data stops showing.
When I download a copy of that online refreshed pbix and look at it (without refreshing on desktop), the data is in the Date View table and doesn't show in the visual. That is shown in the two screen shots above.
I have rebuilt the table from scratch. Checked all filters. Removed all slicers. Built new PBI file using the Dataset from this one.
We have compared versions of Connectors and Settings.
Built a measure" __CalculatedSum = CALCULATE(SUM(DSR_Collections[Collections (Net)])) and you guessed it, BLANK
Of course as soon as I refresh on my desktop, data populates as seen below:
and looks exactly the same in Data View:
Solved! Go to Solution.
This has been resolved.
Interestingly, as stated above. After an online refresh and downloading complete pbix file, I could see the data in the Data View. However, if I went to the dataset and selected Analyze in Excel, the data was not there. I can not explain why it would be in the Data View (sorry).
Ultimately what happened was with a connector update it brought some data over as "nulls" and not "zeros". So those two calulated columns were failing. Inserting a Replace Values (null = 0) resolved this sneaky issue.
This has been resolved.
Interestingly, as stated above. After an online refresh and downloading complete pbix file, I could see the data in the Data View. However, if I went to the dataset and selected Analyze in Excel, the data was not there. I can not explain why it would be in the Data View (sorry).
Ultimately what happened was with a connector update it brought some data over as "nulls" and not "zeros". So those two calulated columns were failing. Inserting a Replace Values (null = 0) resolved this sneaky issue.
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Ask questions in Eventhouse and KQL, Eventstream, and Reflex.
User | Count |
---|---|
84 | |
83 | |
64 | |
61 | |
55 |
User | Count |
---|---|
179 | |
108 | |
105 | |
71 | |
70 |