Problems with visualizations following Browser Refresh

[cmaier]

I have a Power BI report that I have written in Desktop. Relevant visuals pictured here.

Those numbers are correct.  When I publish it to the service, before I connect it through the gateway, the data remain correct (Service version on the far left, local Desktop version on the far right).

When I connect it to the gateway and refresh the semantic model, the data remains correct (Service version on the far left, local Desktop version on the far right).

However, if I refresh the browser (Google Chrome), or navigate away from PBI Service and then back, I get the following (Service version on the far left, local Desktop version on the far right).

I did not click anything, I did not apply any new filters. I did not interact with the report in any way other than opening it.  Why is it suddenly different, and how do I fix it?

I have cleared the browser cache. It did not work. I have refreshed the published report again. It didn't work. I have refreshed the Desktop report to confirm what I think to be the correct numbers are correct. They are.  They only thing I have found that fixes this issue is deleting the semantic model from PBI Service, and republishing.  Even then it only stays correct until I navigate away from the page, and then it is back to the last image above.

The "return to default filters button" (a green undo button next to copilot) is not available becasue I haven't interacted with anything. There is no RLS at play because I am the report author and workspace Admin.  RLS roles exist, but have not been populated because the workspace has not yet been made available because we are running into issues like this.

[Anonymous]

Hi @cmaier 

Are you applying bookmark in report ? What is the data source you are connecting to? When did this happen? Is this the first time you are using that data source?

Best Regards,
Community Support Team _ Ailsa Tao

[cmaier]

Hi @Anonymous 

No, there are no bookmarks on the report in question.  As for when, I noticed it last week. The report has been published for a couple of weeks while I am building out the work space.  Last week I was asked for a number from that report and we noticed it was wrong.

The source is a SQL Server.  This is our first time using PBI for anything, so it is very possible I'm doing something wrong.  I've done a little more investigating, and I think it might be an incremental refresh problem.  There's A LOT of data in here, and my organization wants to have like 7 years worth available, but new data are being added everyday.  So I set up incremental refresh to refresh only the last couple of days daily.  However, I am now seeing that my org's data structure is such that the queries to get it into PBI are only partially foldable, so maybe that's causing the problem.

Ideally, i would want a moving time window of data available in the report, and I'm not sure that's doable without incremental refresh.

Any insight is appreciated.

[Anonymous]

Hi @cmaier 

I would suggest that you can use SQL Profiler to trace down the query statement and then execute this query in SQL to see the results returned. Trace the query statement when you refresh the model and then trace the query statement when you refresh the browser. Compare the two query statements with different results and determine the cause of the problem.

Run SQL Server Profiler - SQL Server Profiler | Microsoft Learn

Best Regards,
Community Support Team _ Ailsa Tao