Forum Discussion
Sharepoint Report Refresh?
Hello BI-Community,
we have a report embedded in a Sharepoint site. In this report we have a map showing locations of moving objects. The underlying data (long/lat) is refreshed evey 15 minutes. Our issue, however, is that the positions of the objects do not change in the embedded report unless we refresh the browser window or interact with slicers in the report. Is there a way to keep the information in the report up to date without any user interaction?
KR
MA
15 Replies
- MAAdvocate I
thank you for the info! However, I have yet to make it work. I tried it with "&refresh=1", but the report is still not refreshed one hour after the last data upload.
However, I might not be using the embedding feature as intended. The MS rep in our company told us not to use the embed code directly in a Sharepoint webpart. Instead, we save the code in a .txt file and display the file in a webpart. Not sure if this is part of the problem, but this is currently our only option.Wish you the best and hope you were able to solve your issue with this fix.
- v-ljerr-msftMicrosoft Employee
Hi MA,
According to your description above, I would suggest you try the Auto Refresh extension for refreshing your web pages automatically in this scenario.:smileyhappy:
Regards
- MAAdvocate I
Thanks for the suggestions, but it seems the issue is not on the browser side. If I update the report and reload the sharepoint page where it is embedded, nothing happens. The only way I can force a refresh is if I select a slicer on the report page and then unselect it to return to the original refreshed view.
- JordiAdvocate I
Sounds like the exact same problem I am having with my embedded reports, only difference is that I am using publish to web and not sharepoint. (https://community.powerbi.com/t5/Service/publish-to-web-won-t-refresh/td-p/135110)
Besides that, interacting with the slicer doesn't help for me either...
- MAAdvocate I
We actually have the same problem. We use the publish to web function to generate the embed code which in turn we put into a Sharepoint web part. Maybe it's because were not using Pro (our IT dep is working on it)....