web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

Power BI Report Timing Out After Upgrade to BC SaaS v26.3 Using Standard Web Services

(7) ShareShare
ReportReport
Posted on by 89

Hi everyone,

Our Power BI team built reports using standard OData web services from Business Central. These reports were working fine until we recently upgraded to "Business Central SaaS version 26.3."

Since the upgrade, the reports are extremely slow to load, and often timeout during refresh. No custom APIs or custom web services are in use — we are only leveraging standard pages exposed as web services (e.g., Customer, Sales Invoice Header, etc.).

I’ve checked for obvious issues like:

  • Any changes in the report design

  • Any modifications in BC (there are none)

But nothing stands out. Has anyone else experienced similar performance degradation with Power BI and OData after upgrading to v26.3? Any tips or tools to help pinpoint the bottleneck would be greatly appreciated.

 

Thanks in advance!

I have the same question (0)
  • Suggested answer
    DAnny3211 Profile Picture
    11,397 on at
     

    Hi Jinesh,

    Performance issues with Power BI reports using OData web services after upgrading to Business Central SaaS v26.3 can be caused by several factors. Here are a few suggestions to help you troubleshoot and improve performance:

    1. Check OData Query Optimization: Ensure that your queries are not retrieving unnecessary columns or rows. Use $filter, $select, and $top to limit data.
    2. Review Page Extensions: Even if no custom APIs are used, check if any page extensions might be affecting the performance of standard pages.
    3. Use Background Data Refresh: In Power BI, enable background refresh and consider scheduling refreshes during off-peak hours.
    4. Switch to Custom APIs: If performance remains poor, consider creating custom APIs tailored to your reporting needs. These are generally more efficient than standard OData pages.
    5. Monitor with Telemetry: Use Application Insights or Azure Monitor to track performance metrics and identify bottlenecks.

    Let me know if this helps!
    If the answer was useful, please mark it as helpful so others can benefit too. 😊

    Best regards,
    Daniele Incalza

  • Gerardo Rentería García Profile Picture
    25,213 Most Valuable Professional on at

    Hi, good day
    I hope this can help you, and give you some hints.

    Power BI Business Central Report - Refresh Timeout... - Microsoft Fabric Community

    Timeout Expired

    Best Regards
    Gerardo

  • Suggested answer
    YUN ZHU Profile Picture
    95,331 Super User 2025 Season 2 on at
    Hi, I'm not sure, it seems to be related to the following update. It is recommended not to use Web Service, using APIs will bring better performance.
    Business Central 2025 wave 1 (BC26): Support for SOAP endpoints is deprecated (Disable SOAP web services on Microsoft UI pages)
    Remove ability to expose a Microsoft page as a OData endpoint (removal)
     
    Hope this can give you some hints.
    Thanks.
    ZHU
  • Suggested answer
    Dynamics_Decoded_Gokul Profile Picture
    451 on at
    Hi, 

    We had a situation similar, raised a Microsoft ticket and we have new set of PBIX file which works fine with 26.3 version, May once the next version released you will also have the better results. 

    if its urgent request you can raise a ticket with MS team. 
     
    Thanks 
    Gokulnath

    This issue seems to standard error, Requesting you to connect with Microsoft support desk.
  • Suggested answer
    Andrés Arias Profile Picture
    4,188 Super User 2025 Season 2 on at
  • Suggested answer
    Steven Renders Profile Picture
    5,672 Moderator on at

    Using standard web services—or standard pages exposed as web services—in Power BI is not recommended. These pages tend to be slow, contain unnecessary code, and are not optimized for efficient data retrieval in Power BI. Moreover, this approach will no longer be supported in the future.

     

    A much better approach is to develop Query objects and expose them as web services, or even better, create Query API objects and import them directly into Power BI.

     
  • Suggested answer
    Sohail Ahmed Profile Picture
    11,136 Super User 2025 Season 2 on at

    After upgrading to v26.3, OData page services can be slow and time out. The recommended fix is to switch your reports to standard BC APIs (v2.0) or create custom API pages instead of using OData pages  APIs are optimized for Power BI and perform much faster.

     

     

     
     
     
    ✅ Mark this as the verified answer if helpful.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 3,143

#2
Jainam M. Kothari Profile Picture

Jainam M. Kothari 1,694 Super User 2025 Season 2

#3
YUN ZHU Profile Picture

YUN ZHU 1,067 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans