Applies to Product - Dynamics 365 Business Central
What’s happening?
Customers are experiencing timeout errors in Power BI reporting caused by the Financial Report KPI web service in Business Central. This issue began on 02/20/2025, with no prior issues reported.
What’s happening?
Customers are experiencing timeout errors in Power BI reporting caused by the Financial Report KPI web service in Business Central. This issue began on 02/20/2025, with no prior issues reported.
Reason:
The timeout errors in Power BI reporting are due to problems with the Financial Report KPI web service in Business Central, specifically occurring in Version 25.3 or later.
The timeout errors in Power BI reporting are due to problems with the Financial Report KPI web service in Business Central, specifically occurring in Version 25.3 or later.
Resolution:
To mitigate this, follow these steps: 1. Open the "Financial Report KPI Web Service Setup." 2. Change the field "Web Service Name" to something different than 'powerbifinance' but ensure it is unique (e.g., powerbifinance2). 3. Click the "Publish Web Service" action. Note that even if the "Published" field still shows False, the new Web Service should be found published on the "Web Services" page. 4. Update the name in the Power BI connector to point to the new Web Service Name.
Additionally, it is important to note that in Version 25.2 and lower, the correct page is 197, while in Version 25.3, it points to page 198. The issue can be reproduced when page 198 is used, but the correct page should be 197.
To mitigate this, follow these steps: 1. Open the "Financial Report KPI Web Service Setup." 2. Change the field "Web Service Name" to something different than 'powerbifinance' but ensure it is unique (e.g., powerbifinance2). 3. Click the "Publish Web Service" action. Note that even if the "Published" field still shows False, the new Web Service should be found published on the "Web Services" page. 4. Update the name in the Power BI connector to point to the new Web Service Name.
Additionally, it is important to note that in Version 25.2 and lower, the correct page is 197, while in Version 25.3, it points to page 198. The issue can be reproduced when page 198 is used, but the correct page should be 197.