Extending Business Central with Power Platform: Patterns That Work

Note: This blog is a personal notebook. I write it to record what I work on, for my own reference, not to publish it on social media or to promote myself. If a post is still useful to you, I am glad, but that is not why it exists.

This post was published on October 28, 2025. Software versions, product features, links, and tool availability may have changed since then. Always check official documentation for the latest information. Some screenshots show small details. Zoom in on the page to see them clearly.

Business Central is a strong ERP system, but it is not a workflow engine, a portal builder, or a mobile app platform. Power Platform fills these gaps, if you know its limits.

Think of a house. AL changes the walls, so you need a builder. Power Platform moves the furniture, so the people who live there can do it themselves.

Problem

In most projects, the core ERP logic is correct but the processes around it are not. Users send approvals by email. Staff count inventory on paper and type it in later. Customers, vendors, and auditors cannot see the data.

AL is right for complex business logic. It is expensive for simple forms, notifications, and read-only portals that a low-code tool solves in a day. Key users also want small automations without a change request.

Why this matters

Power Platform does not replace AL. It moves data and decisions between Business Central and other Microsoft products, so you write, test, and upgrade less AL code. Many customers already own Power Platform rights through Microsoft 365 or Dynamics 365, which lowers the delivery cost.

The risk is maintenance: flows without an owner, apps without documentation, and nobody responsible for ALM (application lifecycle management).

Architecture

Inside Business Central:

  • API pages, standard and custom (APIPublisher, APIGroup, APIVersion), expose data through OData v4 and REST
  • Business events and webhooks tell external tools when something changes, without polling
  • Business Central applies all business rules and permission checks. The connector cannot bypass them

Outside Business Central:

  • Power Automate and Power Apps use the managed Business Central connector, which adds Entra ID authentication to each call
  • Power BI connects through OData or the connector. Reports can sit on a Role Center or a list page
  • Power Pages shows data through Dataverse virtual tables

The Dataverse bridge: Dataverse is the middle layer for model-driven Power Apps, Power Pages, and Dynamics 365 Sales or Field Service. Business Central data appears as virtual tables: nothing is copied, and each read or write calls the Business Central APIs. Dataverse row-level and column-level security applies on top of Business Central permissions.

Pattern Data direction BC enforces rules? Typical use
Power Automate read BC → Flow Yes Notifications, reporting triggers
Power Automate write-back Flow → BC Yes Approval results, status updates
Power Apps canvas Bidirectional Yes Custom data entry, mobile UX
Power BI embedded BC → Report Read-only Role Center dashboards
Power Pages via Dataverse virtual tables BC ↔ Portal Yes Customer/vendor self-service

Demo steps

An automatic invoice approval is a good first scenario: small, easy to validate, and it writes data back.

  1. Prerequisites: A Business Central sandbox, a Power Automate license, and a Teams channel.

  2. Setup: Check that the salesInvoices API endpoint is enabled. It is on by default in SaaS, with no AL extension.

  3. Trigger: Create an automated flow with the trigger “When a record is created (Business Central)” on salesInvoices. Select your environment and company.

  4. Flow logic: Add an Approval action that asks a manager in Teams. On approval, “Create or update record” sets a status field in Business Central. On rejection, the flow notifies the requester.

  5. Verify: Post a draft sales invoice, approve the Teams request, and check the update in Business Central.

Business Central stays the source of truth. The flow passes the same AL validation rules as every other caller.

What is intentionally simple

  • One flow, one entity, one environment, one administrator
  • The standard salesInvoices API only
  • Only the standard Power Automate retry and run history
  • No ALM: the flow is not in a solution

Risks/limits

The license rules are complex. The Business Central connector is premium. A user with only a Business Central license can run flows that a Business Central event starts and that use only Business Central data, within limits that Microsoft defines. A flow that calls Teams, SharePoint, or an external endpoint needs a Power Automate license. Read the current licensing guide, because these rules have changed more than once.

API call quotas. Each license type has a daily request limit, and high-frequency flows reach it in production.

API stability. You own your custom API pages. Rename, re-version, or delete one during an upgrade, and every flow and app that uses it stops, often silently.

ALM is an organizational problem. Managed solutions and pipelines exist, but someone must use them. Flows built outside a solution have no version control and no audit record.

Core ERP logic stays in AL. Keep posting, batch jobs, financial calculations, and anything transactional in Business Central.

Next iteration

  • Put the flows and apps in a managed solution and deploy them with a pipeline
  • Add versioned custom API pages where the standard APIs fall short
  • Link the Business Central environment to a named Power Platform environment
  • Add Dataverse virtual tables for customer or vendor self-service
  • Define governance: approved environments, who can publish, and how flows are reviewed

Closing note

The connector and the API layer are well engineered, but they do not supply discipline. Treat Power Platform components as part of the delivery scope, with the same version control, tests, and documentation as AL code.

← Back to Integrations