Improve Power BI Performance with Business Central Incremental Loading

The demand for Incremental Refresh support between Power BI and Dynamics 365 Business Central has been raised for several years, yet it remains a significant challenge for organizations working with large datasets.

While Power BI supports Incremental Refresh, its effectiveness with Business Central is limited because the connector and standard APIs/OData endpoints do not provide a straightforward mechanism for detecting newly inserted or modified records.

A valuable enhancement would be the inclusion of standard system-managed "Created Date/Time" and "Last Modified Date/Time" fields across key Business Central tables, such as:

• G/L Entries
• Value Entries
• Item Ledger Entries
• Sales Invoice Lines
• Purchase Invoice Lines
• Customer Ledger Entries
• Vendor Ledger Entries
• Items and Master Data tables

Having these fields available by default would enable Power BI Incremental Refresh scenarios without requiring partners and customers to develop custom extensions for each implementation.

Currently, many organizations are forced to implement workarounds such as custom APIs, date-based query splitting, historical/current data separation, or custom audit fields, which increase development effort and maintenance costs.

Native support for change tracking and incremental data loading would significantly improve refresh performance, reduce resource consumption, and make Business Central a more scalable data source for Power BI reporting and analytics.

It would be greatly appreciated if Microsoft could provide an update on the roadmap and future plans regarding Incremental Refresh support for Business Central.

Thank You