What's New: Business Central Integration with Power Platform

Overview

The video walks through what is new in Business Central integration with Power Platform. It starts with Power Automate: a single default entry point for building flows, approval templates that pass environment and company information, and a Get Approver action that reads the approver from the approval user setup table. It then shows AI Builder and Azure OpenAI GPT actions in an approval template that summarizes a sales order for the approver.

The second half covers connector changes (Find One Record, API route defaulting, updated tooltips, triggers in the new designer), the plan to retire V2 actions and V1.0 APIs, and V3 actions with an API category field. It closes with a Power Apps mixed reality sample on GitHub, Dataverse environment linking in the Admin Center, Power Pages, and Copilot in Power Automate and Copilot Studio.

Key points

• From this wave, the Power Automate single entry point is the default view in Business Central and does not need feature management.
• The Get Approver action fetches the requester’s approver from the approval user setup table, so approver parameters need no manual entry.
• An approval template uses an Azure OpenAI GPT action through AI Builder to summarize a sales order (order number, customer, address, lines) for approvers. More templates are planned later in the wave.
• The Find One Record connector action returns a single record through a simple interface, with no OData query syntax and no collection result.
• V2 actions in the connector are now hidden. Existing flows keep running, but full deprecation is planned within the next year, so migrate to V3 actions. This applies to V2 actions, not V2 APIs.
• V3 actions have an API category field to choose Microsoft standard V2.0 APIs, partner custom APIs, or workflow endpoints. Microsoft also plans to deprecate V1.0 APIs.
• The Admin Center can link a Dataverse environment to Business Central. It is the default Power Automate environment unless the user has already configured one.

Features

AL objects mentioned

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

• table “approval user setup table” at 5:08
• page “sales order card page” at 3:31

Not found in BC28-30: table “approval user setup table”, page “sales order card page”.

Quotes

• 2:11 “from this wave onwards we don’t need feature management this is the default view that we will get so the single entry point will”
• 4:28 “information from business central already so we are defaulting these parameters depending on where you”
• 5:08 “have added this new action called get approver which is the action that is responsible to dynamically fetch the approver”
• 7:10 “a new action here uh that creates the summary for the sales order details using GPT using a prompt”
• 13:28 “a plan to deprecate v2 actions fully in”
• 14:29 “you have this new field API category where you can choose the category and of course you have apis coming from Microsoft the standard”
• 15:10 “we have plans of deprecating v1.0 apis”
• 16:13 “this new feature is already available in business Central admin Center”
• 17:33 “that feature is coming as preview later in this wave”

Disclaimers in the video

• 9:10 preview: there will be more of those coming later in the wave
• 13:48 coming-later: we have a plan to deprecate V2 actions fully in the next year
• 15:10 coming-later: we have plans of deprecating v1.0 apis
• 17:33 preview: that feature is coming as preview later in this wave

Presenters (as heard): BU Koto, Monica alja, sand vinaro, keny.