Forum Discussion
Scheduled Refresh Succeeds but Data Won't Update
spinachbisque How quickly are you checking the report after the dataset has said it has refreshed? The Dataset, Report and dashboard are seperate objects and are not all immediately refreshed after the dataset. It is in order. If the dataset refreshes, it is likely it will be 10-15 before the report, and then the Dashboard. You can also initiate a refresh in the report after the dataset.
If you know, and or tried the above, then this sounds like a bug or issue that you should raise in a support ticket or the issues page.
Cheers for the response mhsk ,
I have tested that many times, even making fresh BI reports from scratch to rule out if there's any conflict with the original.
Same issue occurs.
I'm using chrome, and a colleague is using firefox, same issue on both browsers. Data source is a share point list.
In the browser I check the report, confirm successful scheduled refreshes took place overnight.
However while the sched refreshes were successful, the data has not been updated in the report.
Refreshing the browser window or manually refreshing the report in the dashboard makes no difference..
So after this, I check the same report in the desktop application and manually refresh it, this runs and updates the report as expected with the data from the SP list.
I go back to the dashboard again (in chrome) and click refresh, in the report and not the browser.., and it updates the data :/
I didn't publish the report at any point during this test.
It's my understanding that the scheduled refresh should run the same refresh as the desktop application refresh button does, thereby eliminating the need to manually refresh the report from the dashboard at any point.
Am I missing something really simple here?
Any feedback is very welcome.
Advocate IMorning,
I've been pursuing this with the MS support team since it first became an issue for me in April and after numerous email exchanges and screensharing sessions, they don't appear to be any closer to providing a solution.
They believe that the problem is related to the data connectivity mode and specifically an issue with datasets suppossedly configured as DirectQuery remaining as an Import model behind the scenes.
I'd like to be able to provide more input but I'm becoming increasingly frustrated with the entire affair and the most recent telephone calls with the MS off-shore team have been incredibly discouraging.
I'll update this stream if there is further progress.
Thanks for the update on that ims20180411kjb , really appreciate it.
I can fully understand your frustration, and I guess I can empathize to some extent with the MS devs, it might not be a simple fix. An official update from them however would be something at least, to let users know that their frustrations are not going unheard..
I look forward to your (hopefully positive) future updates, will stay tuned.
Thanks again :)
In my case, the server runnning the gateway stuff crashed. I had to re-set iup the gateway stuff on a different box and it's been working as it should since then. I don't trust it won't break again, but so far so good...