With the 2027 Release Wave 1 (version 30.0), Microsoft is reinforcing the separation between the user interface (UI) and application programming interface (API) layers in Business Central. One major change: you can no longer expose Microsoft-authored pages as OData endpoints:
Deprecated features in the client, server, database – Business Central | Microsoft Learn
Why This Matters
Historically, some developers have used UI pages as makeshift APIs. However, UI pages are designed for human interaction—not for stable, long-term integration. They can change between releases without warning, which can break integrations unexpectedly.
Microsoft is now enforcing this boundary to:
- Prevent fragile integrations
- Encourage best practices
- Ensure long-term stability for API consumers
What’s Changing in Version 30.0
Starting with version 30.0:
- You cannot expose any Microsoft-authored page (from apps like Base Application, System Application, or other first-party apps) as an OData endpoint.
- If your integrations rely on these pages, you’ll need to copy the source code and host the page in a per-tenant extension to maintain OData access.
What You Should Do
To prepare for this change:
- Audit your current integrations: Identify any endpoints tied to Microsoft-authored pages.
- Plan your migration: Replace these endpoints with custom extensions.
- Consider alternatives:
- Use Query Objects or Query APIs as web services.
- Design purpose-built APIs that are stable and version-controlled.
The Bigger Picture
This change is part of a broader effort to make Business Central integrations more robust, predictable, and future-proof. By clearly separating UI and API layers, Microsoft is helping developers build integrations that won’t break with every update.
Discover more from think about IT
Subscribe to get the latest posts sent to your email.