Episode Details
Back to Episodes
Go Beyond The Demos: How To Make Copilot Actually Work For Your Business Central Environment
Season 1
Published 6 months, 3 weeks ago
Description
Ever wish Business Central actually did the boring work for you—like reconciling payments, drafting product descriptions, or cleaning up messy workflows—instead of burying you in extra clicks and late‑night Excel? That’s the real promise of Copilot in Business Central online: it’s built in at no extra license cost, but most admins and partners never move beyond the canned demos Microsoft shows on stage. In this episode, we strip away the marketing layer and go into the hidden “System.AI” namespace, Copilot Capability enum, and Copilot & Agent capabilities page so you can turn Copilot from a generic assistant into something wired to your company’s actual processes, data, and tone of voice. By the end, you’ll have a survival checklist you can pressure‑test in a sandbox—including how to register capabilities safely, avoid collisions with Microsoft updates, and give admins clean kill switches if something misbehaves.
THE SECRET MENU OF COPILOT
Copilot’s real power isn’t in the flashy buttons on customer or item cards; it lives under the surface in the System.AI namespace, the Copilot Capability and Copilot Availability objects, and the capability registry devs almost never talk about with admins. We break down how a Capability defines the skill you’re adding (for example, drafting purchase orders, rewriting text in your brand voice, or summarizing complex documents), and how Availability controls where and when that skill appears in the UI. You’ll learn how developers can extend Copilot with new capabilities, how admins can see every registered feature on the “Copilot & agent capabilities” page, and how toggling them on or off turns Copilot from a black box into a controllable, governable framework. Instead of waiting for Microsoft’s next demo scenario, you can design your own AI menu that reflects your approvals, custom fields, and industry quirks—and still keep a big red stop button if something goes wrong.
REGISTERING WITHOUT BURNING DOWN YOUR TENANT
Registering a Copilot capability isn’t magic; it’s AL code. You create an enumextension for Copilot Capability, then use an Install or Upgrade codeunit that calls CopilotCapability.RegisterCapability so Business Central actually knows your feature exists. We walk through why unique names and enum values matter (to avoid collisions with future Microsoft capabilities), why sandbox‑first rollout is non‑negotiable, and how to use versioning and upgrade codeunits to move safely from 1.0 to 1.1 without breaking production. You’ll also hear how the Copilot & agent capabilities page becomes your truth source: if your capability doesn’t show up there with the LearnMoreUrlTxt link, it’s not really registered—and admins won’t know what it does or how to shut it off. Treat registration like production architecture, not a side experiment, and Copilot becomes a stable extension point instead of a late‑night restore job waiting to happen.
METAPROMPTS: TEACHING YOUR AI MANNERS
Once the capability exists, you still need to teach Copilot how to behave, and that’s where metaprompts come in—the “primary system message” that defines the AI’s profile, boundaries, and output format. We explain how metaprompts let you encode your company’s tone, compliance rules, and business logic into the assistant so it stops sounding like a generic HR memo and starts acting like a kno
THE SECRET MENU OF COPILOT
Copilot’s real power isn’t in the flashy buttons on customer or item cards; it lives under the surface in the System.AI namespace, the Copilot Capability and Copilot Availability objects, and the capability registry devs almost never talk about with admins. We break down how a Capability defines the skill you’re adding (for example, drafting purchase orders, rewriting text in your brand voice, or summarizing complex documents), and how Availability controls where and when that skill appears in the UI. You’ll learn how developers can extend Copilot with new capabilities, how admins can see every registered feature on the “Copilot & agent capabilities” page, and how toggling them on or off turns Copilot from a black box into a controllable, governable framework. Instead of waiting for Microsoft’s next demo scenario, you can design your own AI menu that reflects your approvals, custom fields, and industry quirks—and still keep a big red stop button if something goes wrong.
REGISTERING WITHOUT BURNING DOWN YOUR TENANT
Registering a Copilot capability isn’t magic; it’s AL code. You create an enumextension for Copilot Capability, then use an Install or Upgrade codeunit that calls CopilotCapability.RegisterCapability so Business Central actually knows your feature exists. We walk through why unique names and enum values matter (to avoid collisions with future Microsoft capabilities), why sandbox‑first rollout is non‑negotiable, and how to use versioning and upgrade codeunits to move safely from 1.0 to 1.1 without breaking production. You’ll also hear how the Copilot & agent capabilities page becomes your truth source: if your capability doesn’t show up there with the LearnMoreUrlTxt link, it’s not really registered—and admins won’t know what it does or how to shut it off. Treat registration like production architecture, not a side experiment, and Copilot becomes a stable extension point instead of a late‑night restore job waiting to happen.
METAPROMPTS: TEACHING YOUR AI MANNERS
Once the capability exists, you still need to teach Copilot how to behave, and that’s where metaprompts come in—the “primary system message” that defines the AI’s profile, boundaries, and output format. We explain how metaprompts let you encode your company’s tone, compliance rules, and business logic into the assistant so it stops sounding like a generic HR memo and starts acting like a kno