I am currently using the latest Power BI Desktop verison (July-2018) and noticed something odd. I am importing from a table from SQL and then using the power query editor to clean my data. Once the data is cleaned is shows about 400 records. I then proceed to Close and Load data and then only 13 records are available in table. When I refresh and flip back and forth between the query editor and the table in data view the number of records dont match.
I noticed this the other day with another report and after closing desktop and refreshing data a few times it just seemed to fix itself.
Anyone else notice this? I am concerned as my report that end users are using is not showing all records. Strangely the report has been refreshing daily without issue.
Could this be a bug with the July version?
Solved! Go to Solution.
I am experiencing this as well... I also have a query to load from SQL server and when refreshing from Desktop, only a few rows (from January 2016) are loaded. Went to query editor to troubleshoot, refreshed preview, and things seemed to go awry during a split column step. Refreshing preview while selecting this step loads random other dates. Weird.
Just thought to check O365 admin portal and found this... seems it's been an issue for several weeks:
Any thoughts on a work-around for this issue. Like I mentioned in my post above, from Query Editor I should have around 400 transactions, but after Close & Applied I am left with only 13-14 transactions. Very strange. Not sure how to proceed at this point either.
I tried publishing a copy of my desktop file, thinking if I refreshed dataset from PBI service, all would be well, but no luck. You could try "downgrading" to an earlier desktop version. Otherwise, we may have to wait for MS to fix.
Is there a fix to this yet?
I don't see the notification on https://powerbi.microsoft.com/en-us/support/ anymore.
This is really screwing with almost all of our reports.
I saw the notification removal as well and was still experiencing the issue, so I submitted support ticket... spent about an hour this morning with an engineer, who was not able to resolve the issue. Sent an example pbix along with some log files and am waiting to hear back. Once again, I'll let you know if I hear of anything.