Data refresh now not working and getting completely different slicing behaviour in service & desktop

[Nickodemus]

Hi All,

Updated to the July update this morning, and ever since then the data refresh has been behaving very strangely in both desktop and service.

To begin with Desktop refresh started  limiting some tables (querying SQL views) to 1000 rows....... Seemed to fix this be removing a merge in the Power Query, and instead putting the join in the SQL view.

But now....... I'm still not getting a complete refresh in Desktop, and when I publish to Service the slicers on a page of a report are giving a totally different experience in Service to Desktop - Desktop is working as expected.... the slicers are filtering the data for all tables that are related, and showing all available data. BuT...... when published to service and access there, the same slicers seem to be removing a LOT of data in some visuals, leaving only a single point of data in some cases..... (rather than a full  year's worth).

Is anyone aware of anything that could be causing this disparaty in behaviour?? Getting desperate now....

[v-danhe-msft]

Hi @Nickodemus,

Could you please tell me if your problem has been solved? If it is, could you please mark the helpful replies as Answered?

Regards,

Daniel He

[v-danhe-msft]

Hi @Nickodemus,

Based on my test, it could work on my side:

Desktop

Service

I suggest you to test with less data, due to  All DirectQuery requests are sent to the source database, so the time required to refresh a visual is dependent on how long that back-end source takes to respond with the results from the query (or queries).

Reference:https://docs.microsoft.com/en-us/power-bi/desktop-use-directquery#important-considerations-when-usin...

Regards,

Daniel He