Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
Hello,
I have a desktop report that consists of Direct Query to PostgreSQL DB, an excel file and a table combining the 2.
Refresh is possible and quick on desktop. My issue is then I Publish the report to the web. I get only 1 data visualization and slicers, visualizations never refresh. They are stuck at refreshing like this:
I get no slicer options no matter how much I wait. Even if I use custom URL to give Region and LoadType I still get the 1 visualization and no refresh happens. I should mention that Automatic Refresh works perfectly fine, no errors and really quick. So the connection through the gateway to the server, then to Postgre DB and to the excel sources is fine. In Postgre we have opened the IP addresses for Power BI to communicate with the database.
1 hour ago the report was working fine. Now it does not want to visualize anything. I tried re-publishing the report, but this does not help. I got the same issue before, but somehow it resolved itself. Now nothing I do seems to work.
EDIT: After more than 40 minutes the visuals display the following error:
Hi @g_georgiev444 ,
There are a few possible reasons why your report is not refreshing properly when published to the web. Here are a few things you can try to troubleshoot the issue:
If the problem is still not resolved, please provide detailed error information and let me know immediately. Looking forward to your reply.
Best Regards,
Henry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hello @v-henryk-mstf , thank you for the answer.
1. Tried a simple Direct Query and it returns the data in PBi Desktop;
2. Looked at the gateway and it is fine. The Sources are added to the gateway and they are marked with a green checkbox as well, meaning the connection is fine:
3. Refresh history has Completed on all instances with no errors;
4. Scheduled refresh frequency is set to once per day. I manually tried refreshing, but the issue was still present;
5. From what I see there are no limitations. Postgre DB does not limit the fetched results, the .xlsx source is about 200 lines and since refresh is happening on both it shouldn't be an issue. Also, if one of the sources was limiting the number of rows, then it should still show quickly the results - just not all the relevant data. We have checked in the report on Desktop and the numbers correspond to what they should be.
Something interesting to note: Right now (couple of days later) everything works absolutely fine. Without any intervention as nobody was at work. This behaviour is really strange, because we cannot pinpoint when it happens and how to fix it. There is an RPA procces working with this report and we might spam the whole company with empty e-mails.