Publishing a report also resets the data on Service

[Enigma]

Hi, 

I have a report which has a daily scheduled refresh set on it. The refresh works without any issues. The .pbix file is on my local machine. When I open the .pbix file the data shown is about 6 months past(say April'22), which was when the previous version upgrade happened. So that's fine. I never did a refresh from the .pbix because it takes an awful long time and to be honest, I don't care if the data in Desktop is not up to date. The data on the Service is updated as of daily, which is what matters as many people access it daily.

Now, here's the problem I am facing. There are some minor design changes I am making to the .pbix file and whenever I hit Publish, the changes do get published to the Service but the data too gets pushed back to 6 months ago. It shows the data as of April'22 and not as per the last refresh that took place yesterday. On every Publish, it puts the data on the Service exactly as it appears in the Desktop. It's as if I am publishing for the first time, which of course I am not. Also, it's the same workspace I am refreshing it to. the location of the dataset has not changed.
So, to bring the data upto date, I either need to wait till the daily schedule refresh runs, or I have to manually refresh the dataset.

Any reason why this happens?

[Shaurya]

Hi @Enigma,

I am pretty sure this is happening because the pbix has old data which has not been refreshed for 6 months. So when you publish it in service the entire dataset gets replaced by the one in desktop just like the entire report is replaced when you do so some changes and publish.

Since you don't want to refresh in desktop, why don't you publish your report and then, instead of waiting for the scheduled refresh to run, refresh the dataset manually in service!

[Enigma]

That is what I am forced to do rather than wait for the scheduled refresh to run.
But the question remains why does the dataset gets replaced by the desktop data?

[v-easonf-msft]

Hi, @Enigma 

This is by design. 

For now, you have to manually refresh the data before publishing the report.

Best Regards,
Community Support Team _ Eason

[Enigma]

@v-easonf-msft 
Thanks for letting me know, I was not aware of this change. Is there anywhere I can find more information about this change in behaviour?