In a recent announcement, Microsoft confirmed it will no longer be possible to expose a Microsoft Dynamics 365 Business Central page as an OData endpoint, starting with the 2027 Wave 1 release (version 30.0). This change may impact integrations and reporting tools that rely on those endpoints today.
So, why is Microsoft making this change, and what does it mean for you and your customers?
Why is Microsoft Making This Change?
The OData endpoints in Dynamics 365 Business Central expose underlying UI pages as APIs. However, these pages were originally designed for user interface interaction and not programmatic data access. As a result, using OData in this way often leads to decreased performance, inconsistent behavior, and a higher risk of breaking changes when UI pages are modified in updates.
By contrast, the D365 Business Central APIs are purpose-built for integration scenarios. They offer a more stable and performant interface for accessing data. Microsoft is encouraging the move to these APIs to ensure long-term reliability and improved performance for integrations.
eOne Compatibility
In the last few years, eOne Solutions has been adding support for the D365 Business Central APIs across the eOne product suite.
Popdock
All standard D365 Business Central lists and custom Query Builder lists are already powered by API queries, so they will not be impacted by this change. Popdock does allow users to manually add an OData service as a list, but this is an optional feature that we do not recommend due to the inferior performance of the OData endpoints when compared to API queries.
SmartConnect
SmartConnect supports both the standard Business Central API v2.0 and custom APIs. It also supports using bound actions from the v2.0 API as destinations.
If you have any questions, feel free to reach out to support@eonesolutions.com.
