Изменить

Поделиться через

Influence Copilot and agents without extending them

  • Статья

Many Business Central features are directly extensible using AL and offer documented mechanisms to modify or enhance their behavior and functionality. This article explains Copilot and agent capabilities that aren't directly extensible but can work with custom code and content from your extensions. All extensions installed in an environment can influence the output of Copilot and agents.

Approach to extensibility

This table describes how each Copilot and agent capability offers direct or indirect extensibility.

Capability Direct AL extensibility Can work with your extensions Details
Analyze list No  Yes  Copilot automatically works with fields you add to existing pages and new list or worksheet page objects in your extension. No action is required for Copilot to work with your extensions.
Chat No  Yes Copilot can query new pages and tables in your extension. It can include, display, or filter on fields you add to existing pages. No action is required for Copilot to work with your extensions.

Copilot doesn't support fields without a tooltip, fields with the AL property AllowInCustomizations set to false, and the following field types:
  • Blob
  • RecordId
  • InStream
  • OutStream
  • Media
  • MediaSet
  • Notification
  • JsonArray
  • JsonObject
  • JsonToken
  • JsonValue
  • Variant
  • SecretText
While in preview, Copilot can't provide guidance or answer questions based on documentation for your extensions. This functionality is coming in a later release update. Learn more in Chat with Copilot to learn how to use installed add-on apps.
Autofill No Yes  Copilot can autofill fields you add to existing pages, and fields in new card or document page objects from your extension. No action is required for Copilot to work with your extensions.

Learn more about limitations in Autofill availability.
Summarize No  Yes  Copilot generates record summaries that include fields, FactBoxes, and actions from your extension. The fields can be added to existing pages or new card and document page objects. Actions must use the RunObject to open other pages to be included. No action is required for Copilot to work with your extensions.
Sales Order Agent No  Yes Similar to other users, the Sales Order Agent interacts with Business Central using the UI and reacts to the presence of new fields and actions that are made available on pages.

The agent uses an out of the box profile (role) called Sales Order Agent (Copilot) that defines the UI elements the agent can interact with. Using profiles reduces the UI surface that is available to users and agents alike. For example, if the Purchase Orders page isn't included with the profile, the agent can't navigate to it and can't modify the discounts on a sales order because these fields are hidden for this profile. If you want the agent to consider or interact with a field on the Sales Order page added by your extension, customize the Sales Order Agent (Copilot) profile so the field is visible to the agent.
Bank account reconciliation No  Yes  When users ask Copilot to Post Difference to G/L Account, Copilot relies on data from the Text-to-Account Mapping table for a list of specific texts that don’t need to be matched using AI. You can add to this list to reduce cases processed by AI.
Marketing text suggestions No  No   
No. Series Suggestions No  Yes  Copilot can work with any No. Series setting fields added by your extension, if the field follows typical No. Series patterns. Copilot only looks for No. Series fields in Setup tables that include the term "Setup" in the table name. 
E-document matching assistance No  No 
Sales lines suggestions No  Yes  When users choose to keep any sales lines suggested by Copilot, the lines are copied to the sales document, where Business Central automatically triggers field validation and the Copy Document Codeunit. If your extension customizes validation or this codeunit using events, your logic is executed to validate the inserted sales lines.
Create product information No  No   

Improve Copilot and agent output for your extensions

In most cases, Copilot and agents use generative AI to view, learn, and use Business Central like any user. These tasks rely on the quality of the text displayed in Business Central captions, notifications, and messages, and the quality of your online documentation to explain new concepts and business processes introduced in your Business Central extensions.

By improving how your functionality presents itself, you improve the experience both for end users and for these AI-powered features.

Here are some practical examples to improve the quality of Copilot output:

Note

  • Microsoft provides multiple layers of safety for all AI-powered features in Business Central. Some of these safeguards are designed to protect users from harmful content that can be output by generative AI features and might trigger in sensitive business domains such as medical, drugs, legal, or weapons. Customers might experience lower quality output in these domains.
  • You can't extend a Prompt Dialog page When you use the developer tools for Copilot in Business Central. This behavior reduces the chances of others overriding or negatively impacting the AI safeguards built into your experience.

Integrating AI using Developer Tools for Copilot
Developing generative AI experiences overview
Build Copilot user experience