Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
Hi guys, I have an issue.
Our data source moved servers and the gateway throws an error. We can only get it fixed after End-of-Year freeze in July.
I can refresh data in dev desktop and publish it until we can fix the gate.
The only problem is, when opening the report in the web service, it tries to refresh automatically. Breaking some visuals.
Is it possible to disabe auto refresh or the gateway until we can get it fixed?
If so, how?
thanks a mil guys
Ian
Solved! Go to Solution.
"The only problem is, when opening the report in the web service, it tries to refresh automatically. Breaking some visuals."
I don't think that is correct. An unsuccessful dataset refresh does not blit the data over.
The way the service works is :
- a dataset refresh request does not work on the dataset itself but on a shadow copy.
- only if the refresh is successful it will swap the new dataset in and the old out (blitting)
So your failed gateway based refreshes are unfortunate for the service performance (wasting resources) but they have no impact on the existing dataset.
Hi @IanCockcroft ,
Enter the workspace where the dataset is located and click settings.
Best Regards,
Liang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi guys, thanks for you help.
I was able to dig deeper, and its a measure thats not working.
trying to figure out why.
thanks again for taking the time.
"The only problem is, when opening the report in the web service, it tries to refresh automatically. Breaking some visuals."
I don't think that is correct. An unsuccessful dataset refresh does not blit the data over.
The way the service works is :
- a dataset refresh request does not work on the dataset itself but on a shadow copy.
- only if the refresh is successful it will swap the new dataset in and the old out (blitting)
So your failed gateway based refreshes are unfortunate for the service performance (wasting resources) but they have no impact on the existing dataset.
Thanks Ibendlin, we just assumed it was the gateway because we gettin an error.
The crux of the proble is that certain visuals are not working and thats actuall what we are tryng to solve.
It must/might be for a totally different reason.