Business Central 2027 release wave 1: Preparing for OData Endpoint Removal

Key points

• Pages exposed as OData web services will no longer be available from Microsoft-managed pages in version 30, breaking existing integrations
• Three migration paths exist: switch to API 2.0 endpoints, create custom Page or Query APIs, or copy Microsoft pages to custom objects
• Custom page copies can be exposed as OData endpoints by changing the object ID in Web Services configuration, avoiding dependency on Microsoft page updates
• Building custom APIs using Page API or Query API methods provides the most modern and feature-complete solution for long-term sustainability

Quotes

• “Microsoft does not want their Pages beholden to an API, User Interface updates should not be a breaking change to an API.” (Explains the core reason for removing page-based OData endpoints and the architectural shift Microsoft is making)
• “With the release of Business Central version 30, the pages managed by Microsoft extensions will not be available as Web Service endpoints.” (States the specific breaking change that organizations must prepare for within 18 months)
• “Microsoft is only removing access to pages they create; we simply need to create our own replacement page.” (Introduces the backup migration strategy of copying pages to custom objects to maintain current API functionality)

AL objects mentioned

As named in the post. A name that matches one object page by exact type and name links to it; the others stay as named.

• page 21 “Customer Card”
• page “ARDCustomerCardAPI”

Not found in BC28-30: page “ARDCustomerCardAPI”.

Context

• Features: OData web service endpoints, Page exposure as web services, Business Central API 2.0, Custom page APIs, Query APIs, Web Services configuration
• Versions: version 30, 2027 release wave 1

Source: Aardvark Labs, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.