
Hi all,
We've implemented a solution within the last few months where we've embedded a Power BI report inside Business Central, with a Power App inside it, which allows some of our stuff to have access to some reporting information within the ERP that then allows them better make some business decisions.
The content of the report isn't the issue, it's working very well. However, we've been getting a lot of negative feedback that the page will intermittently time-out and refresh, which then also has the impact of all of the filters that the person had been using resetting and them losing where they were up to with their work.
So I suppose there are two questions:
1. Is anyone familiar with anything in Business Central that would be causing the page to refresh or an area in we can control this better (I'm a BI Developer by trade and I've never seen this issue within Power BI).
2. In addition, does anyone have any advice on how we can get filters to hold within reporting when these refreshes do occur (again, my experience is of the Power BI portal and that space is quite good at having recent filters hold in place)
Thanks in advance,
Hello,
The error about a connection being closed is something we have seen before. It typically happens when too many calls are generated simultaneously by the Power BI backend to Business Central. It's an issue on the Power BI side, not on the Business Central side (the Power BI machines are not able to keep enough sockets open to handle the number of requests, to my understanding). Not sure though if this applies to your scenario, if the environment is on SaaS (BC hosted by Microsoft), feel free to have us look at it. You may need to raise a ticket with Microsoft support via the Dynamics 365 BC partner. You can also look at telemetry yourself after enabling application insights (not sure though if this is something end users can do without help from their valued partner).
If I recall correctly, some time ago our developer talked to the Power BI team, and they said something on the lines of "it's better to provide the service document URL to the OData.Feed function, and then select the right endpoint".
If the end user sets filters himself, then a refresh may get the original published filters renewed. Is that something you see happening here?
Thank you.