Shopify and Business Central both offer extensive features for managing products and variants. Depending on your needs, you can choose different options. In Shopify, where you focus on convenience for customers, and in Business Central, where other criteria are taken into consideration, such as the ability to define an assembly BOM.

We're adding support for export scenarios when Shopify has products with variants, but the list of items is flat on the Business Central side. You can use the Add item as Variant action on the Variants subpage of the Shopify Products page.

Details

The item is added as a Shopify variant under the existing product option (for example, color, material, or title, if the product only had the default variant). If the Shopify product has more than one option, you can’t add the item as Shopify variant.

You can add items as variants if they have their own item variants—however, only the item itself is added, and not item variants.

You can't add an item as a variant if the UOM as Variant toggle is turned on on the Shopify Shop Card page.

Shopify always creates a variant, even if you haven’t defined any. This variant is called Default title. When you add more variants via Shopify Admin, this technical variant entry is deleted. The Shopify connector runs similar logic. When the first item is added to Shopify as a product, the Default title variant is added to Shopify and to Business Central. When you run the Add Item as Variant action, the selected item is added as a variant and the default variant is deleted in both Shopify and Business Central.

When adding an item as a variant, the connector won’t search by SKU or barcode.

Product information overview

For more information, see Effect of Shopify product SKUs and barcodes on mapping and creating items and variants in Business Central

You can extend the description for items, general ledger accounts, and resources by adding extra lines as extended text on purchase and sales documents. Now, you can add extra lines on project planning lines. You can have multiple extended texts, and automatically or manually add them to documents using criteria that gives you an extra capability to communicate important information to customers, vendors, and employees.

For example, you can automatically add a particular text, such as details about a special price, to project planning lines on all your German projects for a limited period.

To define extended text for an item

1. Open the card for an item that you want to add extended text to, and then choose the Extended Text action.
2. Choose New.
3. Fill in the Code and Description fields.
4. If you want to apply extended text only for projects in a specific language, fill in the Language Code field. To use all language codes, select the All Language Codes checkbox.
5. To limit the dates on which the extended text is used, fill in the Starting Date and Ending Date fields. The Document Date defined in the project planning line is used as a filter.
6. In the Text field, write the extended text.
7. Select the relevant checkboxes for the document types where you want the extended text printed. To include projects, select Projects on the Sales FastTab.
8. Close the page.

You can activate the Automatic Ext. Texts to automatically add an extended text on sales, purchases, or project documents for an item. You can also add the extended text to documents manually.

To add an extended item text on a project planning line

1. Open a project, and then choose a project task with a line for an item that has extended text.
2. Select the line, and then choose the Insert Ext. Text action.

To avoid the warehouse entry table being locked while warehouse employees posts transactions, we now use a number sequence to assign entry numbers to warehouse entries and entries in the Warehouse Register table. This feature is controlled by a feature key, which is enabled by default. However, you can turn it off if needed—for example, if you have an extension that requires the previous behavior.

Six new Power BI apps are available for finance, sales, inventory, purchase, projects, and manufacturing to enable you to run reports and do data analyses in these areas. We're also providing Power BI apps that you can use to get insights into data about your fixed assets and subscription billing. We'll continue to add new capabilities to the apps throughout 2024 release wave 2.

Archiving capabilities for service management are similar to the functionality you might already be familiar with from the sales and purchase areas. You can set up documents to archive automatically, so that you don't need to think about it. With automatic archiving, Business Central creates a new version of the archived document when people do the following:

• Delete service quote or service order.
• Post a service order.
• Convert a service quote to an order.

We're also extending the functionality of contract filing, which serves a similar purpose of storing a version of a service contract or service contract quote. Now, filed service contracts and filed service contract quotes include more fields, such as Payment Method Code or Direct Debit Mandate ID, and also include the following related tables:

• Filed Contract/Service Discount
• Filed Contract Service Hour
• Filed Service Contract Comment Line

You're in full control of archiving. The following list shows the documents and options you can choose when you set up automatic archiving on the Service Management Setup page:

• Archive service quotes: Never (default), Questions, Always.
• Archive orders: Yes/No
• Delete Filed Contracts: Yes/No.

You can also use the Archive action to manually archive versions of service documents, such as service quotes and orders.

To keep the size of your database under control, archived service documents are added to a list of Retention policy tables.

In addition to the Shipping Charges Account field available on the Shopify Shop Card page, we're adding Shipping Charges Type and Shipping Charges No fields to the Shopify Shipment Method page. Adding these fields allows you to more precisely map shipping fee information from Shopify to the sales document in Business Central.

You can continue to use the G/L account defined on the Shopify Shop Card page, but if you define a Shipping Charges Type and Shipping Charges No, those values are used instead.

The Shopify Connector now supports the following types:

• G/L Account
• Item
• Item Charge

Item Charge is automatically assigned to all items on the sales document.

You can also find the Shipping Agent Code and Shipping Agent Service Code fields in the Shopify Shipment Methods page. If you fill them in, they populate the corresponding fields on the sales document in Business Central.

Multiple shipping fees

Shopify lets you add multiple shipment fees to an order—for example, by editing the order in the Shopify Admin. When you receive several shipping fees with a Shopify order, the Shopify Connector uses the first one to initialize the Shipment Method Code, Shopping Agent Code and Shipping Agent Service Code fields in the header of the document.

Be aware that in other cases, Shopify merges multiple shipping rates into one value called Shipping and doesn’t transfer individual rates.

This update enhances the integration between Shopify and Business Central by using the original return location from Shopify for refunds and returns. This improvement ensures accurate location data in credit memos, which reduces manual adjustments and streamlines the returns process.

To turn on the feature, on the Shopify Shop Card page, choose Original > Default Location in the new Return Location Priority field.

The Return Location Priority field offers the following options:

• Default Return Location: This is the default option. It uses the value from the Default Return Location field when creating sales credit memos.
• Original > Default Location: Select this option if you want the connector to find the original location on the Shopify refund or, if applicable, the Shopify return document. If the connector can't find the original location, for example, when an item is restocked in several locations, it uses the Default Return Location defined on the Shopify Shop Card.

You can export posted sales invoices to Shopify as orders by using a new report (batch job). The report is available on the Shopify Shop Card page, or you can use Tell Me search to find it. You can also run the report by using the job queue.

To enable the capability for a specific shop, go to the Shopify Shop Card page and turn on the ** Posted Invoice Sync** toggle.

The sync includes invoices under the following conditions:

• The Shopify Order ID field contains 0.
• The bill-to customer has a mapping in the Shopify Customers or Shopify Companies tables.
• The bill-to customer isn't used as the Default Customer on the Shopify Shop Card or Shopify Customer Template.
• The posted invoice has at least one non-comment line where the No. field has a value.

When you run the report, the following happens in Business Central and Shopify.

Business Central

Update the Shopify Order ID field based on results of sync:

• Successful export – update Shopify Order Id field with ID of order in Shopify.
• Export failed – set "-1"
• Invoice is excluded from sync for a reason listed in the conditions mentioned earlier – set "-2"

The same pattern is used in the Posted Sales Shipment, where the Update Document page lets you replace "-1" and "-2" or "0" to retry the export.

Shopify

The connector uses GraphQL to first create a draft order with header and item lines, and then complete the draft order and convert it to an order.

Headers and lines

The following fields are exported on the order header:

• The mapped bill-to customer/company is used.
• The Fulfilment Status field shows Fulfilled. Tracking Details don't synchronize.
• The Paid Status field shows Paid or Partially Paid, based on the customer ledger entry linked to the sales invoice. For partially paid, it shows the Remaining Amount field.

The following fields are exported on the order lines:

• Items (item variants) that are mapped export as products.
• Items that aren't mapped and lines of other types, such as G/L Account or Item Charge lines, export as custom products in Shopify.
• Shipping charges in Shopify aren't created. The shipping cost is registered as a custom product in Shopify.
• The new setting on the Shopify Shop Card page lets you avoid exporting invoices with non-mapped items. Turn on the Items must be mapped to Products toggle to exclude posted invoices from sync if there's at least one line of type Item where the selected item isn't mapped to a product or variant in Shopify.
• Tax amounts. Because the Graph API doesn't currently support the TaxLine object, the calculated tax is added as a custom product. Tax information from Business Central won’t be available in the tax report in Shopify Admin. To avoid Shopify recalculating taxes, orders are marked as Tax Exempt.
• Quantity, in whole numbers. Shopify doesn’t support fractions.

Impact on the process of synchronizing orders

Synchronization imports the order and checks whether it was exported earlier. If it was exported earlier:

• It marks the order as processed.
• It adds a link to the posted sales invoice (related documents, should happen automatically because the Shopify Order ID is already populated). Shopify might automatically archive Fully Paid and Fulfilled orders, and the synchronization won't process them.

Deal with updates

In Shopify, because the order is already fulfilled, the only meaningful changes are Notes, Payment Status, and payment transactions. If payments are processed in Shopify, refunds and returns are as well.

In Business Central, changes aren't tracked. Currently, if you want to mark the order as paid, use the Mark as Paid action on the Shopify Order Card page.

Shopify's platform includes data models for fundamental commerce concepts out of the box. However, commerce is diverse and often requires more complex or specific data models. The custom data platform enables you to extend Shopify's data models and create your own by using metafields. Metafields are a flexible way to add and store additional information about a Shopify resource, such as a product or variant. The additional information stored in metafields can be almost anything related to a resource. Some examples are specifications, size charts, downloadable documents, release dates, images, or part numbers.

We're adding the ability to import and export data stored in metafields into Business Central. Also, we're providing an extensibility model that allows developers to map standard or custom fields, attributes, or other related entries in Business Central to metafields in Shopify.

You can see and edit metafields using the Shopify Metafields page, which you open from the Shopify Products and Shopify Variants pages.

To integrate Field Service with service management features in Business Central, you must have a Premium license. When you do, on the Company Information page in Business Central, you must set the User Experience field to Premium.

You can enable the integration in the Integration Type field by selecting Project (default), Service, or Both in the following places:

• In the Set up integration to Dynamics 365 Field Service assisted setup guide.
• On the Dynamics 365 Field Service Integration Setup page.

When the Integration Type field is set to Service or Both, the following things happen when you enable Field Service integration:

• Adds integration table mappings for service order types, service documents, service lines, and service item lines.

• Turns on the Archive Orders toggle on the Service Management Setup page.

• Makes the Service Order Type field on service orders mandatory because the Work Order Type is mandatory on Field Service work orders.

• Fields in the headers on service orders and work orders transfer information, such as the Service Account, Billing Account, and Work Order Type.

• Service Item Lines and Work Order Incidents in Field Service transfer information about the customer assets being repaired.

• Service Line fields and Work Order Products and Work Order Services fields, such as Qty. to Ship, Qty. to Invoice, and Qty. to Consume.

When a technician marks a work order product or service as Used on a work order with a specific work order type, the lines sync to a service order. Consumption is also posted, based on settings on the Dynamics 365 Field Service Integration Setup page.

During consumption and invoice posting in Business Central, the consumed and invoiced quantities are updated on the original work order product and work order service lines in Field Service.

If you choose Enable Inventory Availability by Location when you set up the integration, you can view the allocated product quantity from work orders in Field Service as part of the gross requirements in Business Central's inventory availability calculation. Demand generated by orders in Field Service automatically becomes input for planning through synced service orders.

Companies across sectors have increased their adoption of digitalization and are revamping their products and services to accommodate subscription-based business models.

You can now support many different types of subscription scenarios in Business Central. There's a simple set of processes that let you manage portfolios of the items and services that you bill on a recurring schedule. For example, hardware maintenance, IT support, cleaning services, and so on. You combine the sale of services and items in mixed subscription contracts that hold information about the items, services, and billing schedule.

Templates simplify the process of creating subscription contracts by standardizing the parameters and schedules for recurring billing. You can manage current pricing and plan for future price updates. On the accounting side, posting accruals to balance sheet accounts is automated, and revenue or expense is assigned to the correct periods in the income statement.

The new module comes with:

• Contracts for which you do recurring billing for items and services.
• Billing schedules with flexible parameters that cater to typical use cases for recurring billing.
• Usage-based billing.
• Automated billing.
• Deferral integration.
• Revenue recognition based on billing schedules.
• Contract updates (parameters and prices).
• Standard reports for contracts, customers, billing schedules, recognized revenue, future billing dates and amounts, and so on. Most reports are available as Power BI reports.

Subscription billing is included in the Essential License.

When you adjust currency exchange rates for bank accounts, you can choose to post these adjustments to realized or unrealized gain/loss accounts. This option is available on the Bank Account card in the Posting FastTab.

When a customer completes their checkout in the online store, the information about their payment is saved as a Transaction. There can be multiple transactions linked to an order— for example, a customer might use a gift card to pay some of the cost and then use a credit card or PayPal for the remaining amount. The payment transactions in Shopify synchronize with the orders and you can view them on the Shopify Orders page.

There are several options for processing imported payment transactions in Business Central. This release offers an extra option that's helpful in cases where several payment methods are involved. The gift card scenario is probably the most common, but there are also store credits, which were recently added to the Shopify admin.

Sample scenario

This example scenario involves the following parties:

• The buyer, who is the person who buys goods from your Shopify online store.
• The merchant, which is your company.
• The payment provider, which is the company that facilitates payment processing for you. The provider can be Shopify Payments or a third party.

How the money flows

The buyer buys goods from an online store. The last stage is to process their payment.

The buyer pays part of the amount with a gift card (or store credit), and the remaining amount with a credit card, PayPal, or a local payment method such as MobilePay in Denmark.

The merchant can see the issued gift card and information about its use in Business Central.

Depending on the payment provider, the merchant might see the money in their account with the payment provider, including both the amount received and the amount deducted for the provider's commissions. Payment providers often take a commission from each transaction, and in some cases they also have a fixed fee.

Depending on the payment provider, the merchant either transfers the money to their bank account (payout) manually or automatically within a defined period. For example, one time per day, per month, and so on.

Depending on the bank, the merchant can see the incoming transaction in their bank account via online banking or their bank statement.

Reconcile transactions and bank statements

The merchant imports a sales order to Business Central and posts the shipment and invoice. Business Central creates a customer ledger entry of the type Invoice with the full amount, and sets Open to Yes. The remaining amount equals the invoiced amount.

The merchant processes the imported Shopify transactions in the Transactions list. They apply filters, and then use the Suggest Shopify Payments action to transfer the transactions to the general journal. Alternatively, the merchant can use the Suggest Shopify Payments action on the Cash Receipt Journal page.

The merchant reviews the lines, and notices that the applied documents are selected automatically. They post the journal, and Business Central creates a customer ledger entry of the type Payment and applies it to the corresponding entry of the type Invoice.

The merchant imports their bank statement using a payment reconciliation journal or bank reconciliation journal with one or more transactions that represent the transfer from the payment provider to bank account.

Currency handling

The Shopify connector imports orders and transactions in Shop Currency. If you configure Shopify to use different currencies based on country, that might lead to some differences. For example, in a store where the local currency is Danish Krone (DKK), an order for a German customer totaling 13.95 EUR converts to 409.53 DKK in sales. However, the payment transaction shows 409.48 DKK.

The process of creating purchase orders from projects is similar to the functionality you might already be familiar with from the sales area. The process lets you create purchase orders right from a project. It shares the same algorithm as the Order Planning worksheet, which means it doesn't require elaborated setup to produce recommendations, but it's intelligent enough to analyze demand and supply for required items.

To create one or more purchase orders from a project

To create a purchase order for the quantity of each item the project is missing, use the Create Purchase Orders action.

1. Choose the Lightbulb that opens the Tell Me feature icon, enter Projects, and then choose the related link.

2. Open a project that you want to purchase items for.

3. Choose the Create Purchase Orders action.

4. The Create Purchase Orders page opens and shows a line for each item on the project. Lines for both fully available quantities and unavailable quantities show by default. Unavailable quantities aren't available. To show only unavailable quantities, choose the Show Unavailable action.

5. The Quantity to Purchase field contains the unavailable quantity. To purchase a different quantity, edit the value in the field.

   Note

   You can also change the Quantity to Purchase field on unavailable lines, even though they represent fully available quantities.

6. You can also turn on the Reserve toggle if you want to reserve the quantity on the purchase line against a demand instead of populating the Project No. and Project Task No. fields of the purchase line. To add the Reserve field, personalize the page.

7. Select OK.

This process creates a purchase order for each vendor from which you purchase the items on the project, including any quantity changes that you made on the Create Purchase Orders page. You can continue to process the purchase order or orders, for example, by editing or adding purchase order lines.

Later, you can review the purchase lines linked to the project either from the Project Card page or Project Planning Lines by choosing the Purchase Lines action.

As in other cases that involve advanced inventory processes, such as reservation, warehousing, and assemble-to-order, the project's status must be Open and the Apply Usage toggle must be selected.

Based on feedback from our customers, we've made it easier to complete several business processes in projects and service management.

To speed up the process of creating invoices for projects, we’ve added the Create Project Sales Invoice action to the Project Card page. Now you can create invoices without having to leave the project information. Additionally, we’ve made it faster to access and work with details about projects by adding the following actions to the Project List page:

• Assembly Orders
• Put-away, Pick, and Movement Lines
• Registered Pick Lines
• Project WIP Cockpit

We’ve also done some renaming in projects. The Project WIP page is now named Project WIP Cockpit, which makes it easier to distinguish it from other Project WIP pages and actions.

To improve service management features, we’ve added some useful fields to several pages. The addition of the Customer Name field on the Service Items page lets you identify the customers that use the items. Also, to make it easier to find records by searching for your reference numbers, we’ve added the Your Reference field to the following pages:

• Service Invoice
• Service Orders
• Service Quotes
• Posted Service Invoice
• Posted Service Invoices

We've streamlined the Make order process for both service and sales. When you convert a service quote to an order, you're prompted to open the newly created service order and process it.

We are adding Service Item Worksheet as an option on the Report Selection - Service pages. The worksheet contains the currently available Service Item Worksheet report, but you can change it if needed. You can also add reports if you want to print more than one report per document type, for example.

To give you more information about when and where an item is available from the context of a business task, we're adding the Item available by action to the Project Planning Lines and Project Journal pages. You can also view the availability of each item per location, by event, or by period.

Shopify releases a new API version every three months at the beginning of the quarter and supports each version for 12 months. These API releases might bring bigger changes—that’s why it's important to uptake Shopify API versions in major releases of Business Central. Typically, new versions of APIs increase stability and security, and enable additional capabilities. Starting with this release, the Shopify connector uses the Shopify API that was released in July 2024.

The new version introduces changes in various areas that aren't directly visible. The changes that have direct impact are listed below.

• Shopify Connector now supports up to 2,000 variants per product, which is the capability that Shopify announced in the winter editions. You just need to wait until Shopify enables that capability in your store.

• There's a new way to deal with risk assessments. Shopify now supports two levels and external providers. The connector continues to import both risk and sentiments. However, there isn't a single value that represents the risk associated with an order, which is why this information doesn’t display on sales orders or invoices.

• When you enable the connector, it imports the default weight unit of measure from Shopify and uses it when it sends the weight of the product. You can change whether the Net weight field in Business Central stores values with different units of measure.

• The Gift card property is now available on sales lines, and not only on the product, which lets the connector recognize custom discounts, usually sold via POS, and process them as normal discounts.

• The Location Code field in the Shopify Order header is discontinued. The connector won’t import data from the Location or Physical Location fields. Instead, it relies on location information in the order fulfillment lines. Sales documents contain a location only on their lines, and not in the header.

• The use of units of measure is aligned. Imported sales documents use the sales unit of measure defined on the item card. The sales unit of measure is also used to calculate prices and discounts. We've aligned the unit of measure to use when synchronizing inventory to also use the sales unit of measure.

In addition, we implemented a number of improvements that aren't related to the new API version, but that improve the general usability of the connector.

• The Linked to Documents FactBox is available on the Shopify Orders page. You can open an order, invoice, or shipment from the list.

• The Shpfy Doc. Link To Doc. permission is added to D365 BASIC to enable warehouse processing and other posting activities without the need to grant full Shopify permissions.

• The Tax ID value is now imported from the company location in Shopify. Note that the data isn't used when you create or update a customer because in various localizations that field has a different destination.

• The Shopify Activities part has a default color configuration, which makes it easier to notice issues with synchronization.

To include translations in the product synchronization, follow these steps:

1. Choose the Tell Me icon, enter Shopify shops, and choose the related link.
2. Select the shop to open the Shopify Shop Card page.
3. To open the Shopify Languages page, choose the Languages action.
4. To import languages enabled on Shopify, choose the Refresh action. Notice that the primary language isn't listed. For the primary language, continue to use the Language Code field in the Shopify Shop Card.
5. For each language you want to include in the synchronization, fill in the Language Code field and turn on the Sync translations toggle.

Translations will be included every time you run the Sync Product task either manually or by using the job queue.

More information

• A new Shopify permission (scope) is needed: read_locales. You must request a new access token.
• The first export of items, initiated by the Add item to Shopify action, doesn't include translations. You need to run Sync product and turn on the Can Update Shopify Products toggle.
• Marketing text is only added for the primary language.
• Extended texts are added for each language, plus extended texts where the All Languages toggle is turned on.
• Attributes are added for each language. If a translation is missing, the primary language is used.
• Item translations are added for each language if a translation is defined.
• Variant translations aren't used because the connector only exports the variant code, and not its description.

Extensibility impact

The CreateProductBody procedure in the Product Export codeunit takes language codes as parameters so it can be used for each language. Now this procedure is called multiple times according to the list of selected languages. Because it contains the OnBeforeCreateProductBodyHtml and OnAfterCreateProductBodyHtml events, those events are now triggered multiple times per item. The events now include the language code as a parameter, so you can skip translation or add your own logic.

Default values on documents can speed up data entry. If you want new lines for general ledger accounts on sales and purchase documents to have a quantity of 1 by default, on the Sales & Receivables Setup and Purchase & Payables Setup pages, turn on the Default G/L Account Quantity toggle.

As a continuation to our multi-release effort to ensure that project management features benefit from the rich warehouse capabilities in Business Central, you can now use locations configured for directed flows with projects.

Businesses pick items before they're consumed in different ways. The process depends on how their warehouse is configured. When you want to specify either a default Location Code on the Project and Project Task Lines Subform pages, or enter a Location Code on Project Planning Lines, you can now also use locations where the Directed Put-Away and Pick toggle is turned on.

To create or register a pick document, you can use the Create warehouse pick action under the following conditions:

• The Status of the project is Open.
• The Line Type of the project planning line is Budget or Both Budget and Billable.
• The Type of the project planning line is Item.
• The Project Consump. Whse. Handling is Warehouse Pick (mandatory) , which is now available when Directed Pick and Put-away is selected.

You can also create warehouse picks using a pick worksheet. The pick worksheet lets you organize pick information before you create warehouse pick instructions. You'll need to fill in the a To-Project Bin Code field on the Location Card page.

Limitations

You can't use the Project No. and Project Task No. fields in the purchase order together with locations where the Directed Put-Away and Pick toggle is turned on. You must post receipts and consumption separately with the fully directed warehouse flow.

In this release we have added four Excel report layouts that cover the consolidation and fixed assets areas:

• Consolidated Trial Balance (Preview)
• Fixed Asset Details (Preview)
• Fixed Asset Analysis (Preview)
• Fixed Asset Projected Value (Preview)

The report layouts are available through search and the Accountant home page.

The content of each report covers the content of one or more existing RDLC reports, and gives you the underlying data so you can create custom reports.

Inventory cost adjustment in Business Central is the process of ensuring that item costs are accurately reflected by adjusting costs based on changes in purchase prices, revaluations, or applied costs through transactions such as sales, consumption, and transfers.

It's essential for maintaining correct inventory valuation and COGS, especially when businesses use costing methods such as FIFO, LIFO, or Average. You can run cost adjustment automatically or manually, and it affects historical transactions and financial reports. To avoid discrepancies, it's important to set up cost adjustments correctly and regularly monitor them.

We're introducing multiple enhancements to the cost adjustment process to improve its performance for larger workloads and allow easier troubleshooting and monitoring:

• Identified and eliminated bottlenecks based on telemetry data and code analysis, which significantly improves processing speed.
• Introduced period-by-period and selected production and assembly order adjustments for high-transaction items, which lets you control processing scope.
• Added notifications for potential issues, suboptimal settings, high volumes of entries, and data discrepancies.
• Developed a tool to visualize adjustment progress, which helps you analyze performance issues and identify inefficiencies.
• Enabled item-by-item adjustments, which ensures that partial progress is saved in long-running processes to prevent full reruns if things go wrong.

The list of standard reports for financial reporting is expanded to include five new reports. In addition, a set of five new row definitions and 12 column definitions are provided. You can combine them to create more than 25 new reports.

The following table lists the new reports:

The new row definitions have the same names and descriptions as the reports.

The following table lists the new column definitions:

Financial reporting demo data - planned to ship in the 25.2 minor release

Financial reporting is at the core of every business, and when evaluating business management applications it's often desirable to view the reporting capabilities as they would look for a running company. You can generate the new demo data by running the Contoso Financial demo data from the Contoso Demo Tool tool page. The data will contain three years of G/L entries, broken down to dimensions with a budget for the current year for variance analysis reporting.

If you use Shopify B2B, you can configure the connector to synchronize prices for Shopify catalogs that are linked to B2B customers. The following steps explain the process.

Sync catalogs from Shopify

1. Select the Tell Me icon, enter Shopify Catalogs, and select the related link.
2. Select Get Catalogs.
3. Select the entry for which to define and export prices, and then fill in the fields as necessary.

You can use two strategies. One is the default strategy, where you can use settings similar to the ones for synchronizing the Price and Compare at Price fields for Shopify products (Shopify variant). The following table describes settings for the default strategy.

The second strategy is to use the new Customer No. field. In this case, the connector uses the customer to calculate the price. It ignores other values defined in the Shopify Catalog entry, and uses the Customer Price Group, Customer Discount Group, and Allow Line Discount fields from the customer card. Use personalization to add the Customer No. field to the Shopify Catalog page.

After you enter the settings, turn on the Sync Prices toggle and choose Sync Prices to start synchronizing catalog prices.

You can now integrate, configure, and customize Field Service warehouses with Business Central's locations. To manage the synchronization of data, we've added a unidirectional (from Business Central) integration table mapping between Business Central locations and warehouses in Field Service. To use the new integration table mapping, in Business Central you must turn on the Location Mandatory toggle on the Inventory Setup page.

Business Central syncs locations with the following settings on the Location Card page:

• The Use as In-Transit toggle is turned off.
• Project Consump. Whse. Handling is different from Warehouse Pick (mandatory).
• Assm. Consump. Whse. Handling is different from Warehouse Pick (mandatory).

On the Locations and Location Card pages, you can use the Warehouse action to open a coupled location in Field Service, sync it, set up and delete couplings, and view sync logs.

You can use Open in Business Central in Field Service to open a location in Business Central that's coupled to a warehouse in Field Service.

Choose Enable Inventory Availability by Location in the Dynamics 365 Field Service Integration Setup page or in the Set up integration to Dynamics 365 Field Service page.

When you enable inventory availability by location, a new Inventory Availability by Location API becomes available as a Dataverse virtual table and a synthetic relationship is created between this virtual table and the native Products table in Field Service.

In Field Service, on the Products page, technicians can check how much of particular product is available at a warehouse they specify.

Autofill is a new capability of Copilot in Business Central:

• When drafting a new record or editing an existing record, Copilot can suggest values for some of the editable fields on the page.
• Autofill is available for fields (but not rows or columns) in card and document pages such as Customers, Sales Orders, Items, or even your own custom pages.
• Suggestions are grounded in your company data, and might be based on recently used values, frequently used values, or intelligent selection from a choice of values in a lookup or option field. They can also be AI-generated depending on the field and context.
• Copilot simply suggests the value to you, giving you the opportunity to review where the suggestion originates from. Ultimately, users remain in control and decide to apply that value, discard it, or replace it.
• Available later this wave: Copilot will automatically search the web for more information and provide suggestions for customer or vendor contact details, product codes, and similar fields that typically contain public information.

Try it out

Tip: You can get hands-on with Autofill as early as March 2025 using sandbox environments on preview version 26.

Look for the sparkle icon on fields to ask Copilot for suggestions.

Copilot makes suggestions for multiple fields within the FastTab (group). Use the information icon to understand how Copilot made the suggestion.

Review, keep, or discard a suggestion. You can also do this in bulk by keeping or discarding all suggestions.

About security, privacy, and AI

Copilot is built on Microsoft's comprehensive approach to enterprise security, privacy, compliance, and responsible AI. Our philosophy is that your data is your data: customer data in Business Central is not used to train AI models.

Read the FAQ for Copilot data security and privacy for Dynamics 365.

Join the conversation

We're excited to have you with us on our Copilot journey.

Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the forum at aka.ms/bcIdeas, or join the partner community discussion on the Dynamics 365 Business Central Partner Community Network on Viva Engage (formerly Yammer) to help us shape the future of AI in Business Central.

Every company has expenses. Some relate to the supply chain, and others to operating costs like rent, utilities, leasing, food, phone bills, and software subscriptions. These operating costs, known as overhead expenses, are the first focus of the Payables Agent. They are often received as email attachments or through other channels.

Sourcing files and attachments related to purchase of overhead expenses

In the first version, the Payables Agent can source purchase attachments (PDF files) from a Microsoft 365 email account where vendors send their invoices. The agent can also import PDF files from a shared SharePoint folder where the accountant and other employees place files to be processed. These invoice documents are imported into E-Documents in Business Central for further processing. After importing the documents, the agent moves the files to an archive folder.

Processing imported purchase attachment and files

Once files are imported, Azure Document Intelligence processes them using Optical Character Recognition (OCR) technology. The results are stored in Business Central in the E-Document. An updated PDF attachment viewer lets users validate the OCR processing by viewing the attachment in near-full screen with position overlays of captured information like amounts and descriptions.

Creating purchase invoices

When Azure Document Intelligence processes a purchase attachment, the Payables Agent creates a purchase invoice document, ready for further approval and posting. The agent uses various predictors and indicators for creating these invoices, like the company's available purchase history, accounting policies, or others specified when setting up the agent. The goal of the Payables Agent is to streamline the entire flow from identifying and importing purchase attachments, capturing relevant information to categorize the expense, registering the expense correctly in the general ledger, to creating purchase documents.

In the future, the Payables Agent will handle increasingly complex scenarios and company-defined rules, manage supply chain expenses, and match with open purchase orders, while also supporting E-Invoices received through other channels, like PEPPOL and other access points, or vendor invoices pushed into E-Documents via its native API.

With this feature, you can:

• Author tests for your prompt dialogs using a familiar framework in AL and Visual Studio Code.
• Organize your test datasets based on purpose and prompt variations.
• Implement automated verification depending on your feature use case.
• Run tests as fully automated or semiautomated.

Copilot's chat capabilities have been enhanced with the following:

• Users can ask questions about content from installed add-on apps, such as new pages, fields, and business processes.
• Copilot explains and guides based on documentation provided by the apps installed in your Business Central environment.
• The Ask Copilot icon is available in tooltips for custom fields that originate from installed apps.

About security, privacy, and AI

Copilot is built on Microsoft's comprehensive approach to enterprise security, privacy, compliance, and responsible AI. Our philosophy is that your data is your data: customer data in Business Central is not used to train AI models. For more information, go to FAQ for Copilot data security and privacy for Dynamics 365 and Power Platform

Looking for more details?

• Read the preview announcement for Chat with Copilot
• Learn about Chat with Copilot
• AI FAQ for Chat with Copilot

Tell us what you think

We're excited to have you with us on our Copilot journey.

Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the forum at aka.ms/bcIdeas, or join the discussion on the Dynamics 365 Business Central Partner Community Network on Viva Engage (formerly Yammer) to help us shape the future of AI in Business Central.

The bank account reconciliation feature in Business Central has been enhanced with:

• AI-powered transaction matching that complements rule-based matching and further reduces the remaining unmatched transactions that require review.
• AI-powered G/L account suggestions where Copilot suggests the most likely ledger account to post any residual transactions to and offers the opportunity to remember a specific transaction description for the next reconciliation.
• Built-in demo data for evaluation companies that makes it easier to experience and demonstrate this Copilot capability to others. Demo data is available in English with 23.1 and other languages with 23.2.

Public preview notes

This feature is available as a production-ready preview for production and sandbox environments with any country localization of Business Central and is available for any user language. Production-ready previews are subject to supplemental terms of use. For more information, see Supplemental terms of use for Dynamics 365 preview.

While the feature is in preview, it performs best when the G/L account names, ledger entries, and bank account transaction descriptions are in English.

Availability

This feature is exclusively available for Business Central online.

Looking for more details?

Watch the 20-minute video where the product engineering team at Microsoft shares more details about this new capability.

To access recordings on demand from the Business Central 2023 release wave 2 launch event, register for free at aka.ms/BCLE.

Try it out

To get started, go to the Bank Account Reconciliations page and choose Reconcile with Copilot.

This feature is available with all new production and sandbox environments with Update 23.1.

For upgrading customers, the feature will be automatically enabled with Update 24, but administrators can enable it as early as Update 23.1. To enable features ahead of time, sign in to your online environment and open Feature Management, then enable for all users the item named Feature Preview: Bank account reconciliation with Copilot.

In some regions where Azure OpenAI Service is not yet available, administrators must first consent to business data moving across compliance boundaries from the Copilot & AI capabilities page.

Tell us what you think

We're excited to have you with us on our Copilot journey.

Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the forum at aka.ms/bcIdeas, or join the discussion on the Dynamics 365 Business Central Development Yammer network to help us shape the future of AI in Business Central.

Because product (item) information is spread out across several pages, creating and managing this information can be a time-consuming task. The effort involves looking up information based on existing items, pasting values, and ensuring the new product is ready to transact. Creating variants, dimensions, units of measure, and other item-related information also takes time that delays market readiness for new products.

Copilot can help you add items by reusing information from similar items. Copilot can suggest the following information:

• Substitutions (in preview)
• Dimensions (planned)
• Variants (planned)
• Units of Measure (planned)

When you manage product information, Copilot can assist by suggesting data from similar products (items). Copilot assistance not only reduces the time it takes to create a product, but it also ensures that your products are ready to transact faster than ever before.

In this release, we're starting with a foundation that will help you define similar products (items). You can store similar or interchangeable products on the Item Substitution Entry page. Copilot helps to add this information for current products by searching for similar ones in the database.

About security, privacy, and AI

Copilot is built on Microsoft's comprehensive approach to enterprise security, privacy, compliance, and responsible AI. Our philosophy is that your data is your data: customer data in Business Central is not used to train AI models. Read the FAQ for Copilot data security and privacy for Dynamics 365 and Power Platform.

Try it out

Copilot is available exclusively for Business Central online. To experience this feature, sign in to your Business Central environment, go to the Items list, and activate the link for Substitutes Exist on any item. Then, choose the Suggest substitutions action.

Tell us what you think

We're excited to have you with us on our Copilot journey.

Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the forum at aka.ms/bcIdeas, or join the partner discussion on the Dynamics 365 Business Central Partner Community Network on Viva Engage (formerly Yammer) to help us shape the future of AI in Business Central.

In** 2024 release wave 1** we introduced Copilot that can suggest and assist with creating sales lines on sales documents such as sales quotes, orders, and invoices based on structured input or natural language. This assistance can reduce manual data entry and drive operational efficiency.

Versatile input methods: Copilot can accept various input methods, including free text, files, or prebuilt input prompt suggestions. This flexibility allows you to interact with Business Central in ways that are convenient for you, which further boosts efficiency.

Intelligent processing: Leveraging advanced AI capabilities, Copilot understands the input you provide and uses it to suggest sales lines. This intelligent processing eliminates the need for manual data entry, reduces the likelihood of errors, and saves time. Additionally, Copilot can suggest sales lines based on how recently and frequently the customer on the sales document has purchased from you.

New additions in update 24.2 for 2024 release wave 1:

• This feature is now available in environments localized to Canada.
• People who use Business Central in a language other than English can access this feature.

New additions in 2024 release wave 2.

We continue to improve Copilot in Business Central by adding new capabilities and polishing existing ones.

In addition to the Find product and Find document by reference skills, Copilot can combine them. It can first find documents, and then search for products on document lines. This combination can be particularly useful for companies that often work with blanket orders. The Find document by reference skill now includes sales blanket orders as source documents.

Also, it also now supports units of measure. Copilot can try to use the unit of measure you specify in your prompt, but if that isn't found it falls back to the sales unit of measure for the item.

Attachments are a longer journey that starts with CSV files. Copilot analyzes the structure of an attached file to identify things like field and row separators, date and decimal formats, columns, and headers. It suggests field mappings to fill in product and quantity fields.

Errors and messages that are thrown by the code logic in Copilot prompt dialogs now surface directly inside the dialog rather than in a separate pop-up dialog. There's no additional work required by developers to enable this feature, apart from authoring proper error handling and warnings as you already do today. Both the classic Dialog.Error() and Dialog.Message(), as well as the newer ErrorInfo patterns are supported. In the case of the latter, the title and description will both be shown.

If the code throws more than one message, only the latest will be shown, but the user is told that there were multiple issues. Also, as has already been the case, if an error is thrown, a subsequent message will be suppressed. If the error or message contains line breaks, these are ignored, as opposed to rendering in dialogs.

Example 1: Rendering multiple messages thrown by Message() while in the prompt dialog

The following code snippet illustrates throwing multiple messages, using Message(), when the user chooses the Generate button in a prompt dialog.

page 50110 PromptDialog {     PageType = PromptDialog;      layout     { ... }      actions     {         area(SystemActions)         {             systemaction(Generate)             {                 trigger OnAction()                 begin                     Message('First message, which is not shown in the prompt dialog');                     Message('Last message, which is shown in the prompt dialog');                 end;             }         }     } } 

As a result, when invoking the Generate action in the Copilot prompt dialog, the last message is rendered inline in the Copilot prompt dialog, along with an indication that there were more messages.

Example 2: Rendering an error thrown by Error() while in the prompt dialog

Here we instead change to throwing an Error():

page 50110 PromptDialog {     PageType = PromptDialog;      layout     { ... }      actions     {         area(SystemActions)         {             systemaction(Generate)             {                 trigger OnAction()                 begin                     Error('This is an example of rendering an error that happens in the prompt dialog, e.g., during Generate');                 end;             }         }     } } 

In this case, the error is rendered inline:

Example 3: Rendering an error thrown by ErrorInfo while in the prompt dialog

The final example illustrates using the recent ErrorInfo type.

page 50110 PromptDialog {     PageType = PromptDialog;      layout     { ... }      actions     {         area(SystemActions)         {             systemaction(Generate)             {                 trigger OnAction()                 var                     ErrorInfo: ErrorInfo;                 begin                     ErrorInfo.Title('Error info title');                     ErrorInfo.Message('Error message');                     ErrorInfo.DetailedMessage('Detailed error');                      Error(ErrorInfo);                 end;             }         }     } } 

In this case, the ErrorInfo message part is rendered inline, and the title part is used for the tooltip. The detailed message is ignored.

Tell us what you think

We're excited to have you with us on our Copilot journey.

Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the forum at aka.ms/bcIdeas, or join the partner discussion on the Dynamics 365 Business Central Partner Community Network on Viva Engage (formerly Yammer) to help us shape the future of AI in Business Central.

To use this feature, sign in to your Business Central online environment and follow these instructions. The feature adds the following capabilities to Copilot:

• In addition to using an 80% string match in descriptions for automated matching, Copilot also incorporates item references and G/L mappings in preprocessing.
• If an incoming e-document has lines that aren't present in the related purchase order, it highlights the discrepancy and you can run the Create Purchase Order Line action, which prompts you to specify the Type (G/L account, Item Charge, Resource, and so on) and Number you want to connect. You can change the Quantity for the purchase order line, but keep the same total amount for this line. Afterward, Business Central creates a new line in the Purchase Order and keeps it matched with the base line from the incoming e-document.
• If you enable the new Create matching rule setting, lines that Copilot matches are saved for future use, either as an item reference or a G/L mapping.

Join the conversation

We're excited to have you with us on our Copilot journey.

Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the forum at aka.ms/bcIdeas, or join the partner community discussion on the Dynamics 365 Business Central Partner Community Network on Viva Engage (formerly Yammer) to help us shape the future of AI in Business Central.

This update to the preview includes:

• Availability for more users: Added support for more languages, now including: English, Danish, German, Italian, French, Dutch, Spanish, Portuguese (Brazil), Japanese, Swedish, Finnish, Norwegian, Polish, Russian, Thai, Turkish, Czech, Greek, Korean, Chinese (simplified)

• Flexibility: Copilot can draft analysis tabs using all fields from the list page, including columns that might be hidden.

• Improved control: It is easier to make manual changes to an analysis tab drafted by Copilot, with the ability to navigate back and forth through the history of the tab before finalizing it.

About security, privacy, and AI

Copilot is built on Microsoft's comprehensive approach to enterprise security, privacy, compliance, and responsible AI. Our philosophy is that your data is your data: customer data in Business Central is not used to train AI models.

Read the FAQ for Copilot data security and privacy for Dynamics 365 and Power Platform.

Looking for more details?

• Read the preview announcement: Get to insights fast with Copilot-created analysis tabs
• Analyze data in lists with the help from Copilot
• AI FAQs for analysis assist

Tell us what you think

We're excited to have you with us on our Copilot journey.

Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the forum at aka.ms/bcIdeas, or join the partner discussion on the Dynamics 365 Business Central Partner Community Network on Viva Engage (formerly Yammer) to help us shape the future of AI in Business Central.

In this wave, we evolve chat with Copilot (first announced for 2024 release wave 1) based on community feedback:

• Faster: Copilot fetches records more quickly.

• Better at data inquiries: Copilot generates analysis tabs directly from the Chat pane to help you get to insights about your data. Copilot takes this approach whenever you ask questions that are best illustrated by grouped records or simple math such as totals or averages. Try entering, "Show items grouped by their category".

• Awareness of the current page: Copilot responds to requests to find data from the currently open page, using its ability to filter, sort, and generate analysis tabs to help you get to insights. Try entering, "Which products are blue on the current page?" while the Items list page is open.

• Interconnected AI: Copilot helps you understand how it can provide additional AI-powered assistance on the current page, identifying built-in features as well as extensions to Copilot. Try entering, "What can Copilot do on this page?"

• More knowledgeable: Copilot uses more sources of information from Microsoft Learn to explain and guide. For example, it now includes answers from release plans.

• Tailored answers: When explaining or giving guidance, Copilot only shares administrative and technical answers with people with administrative roles.

• More examples: The prompt guides (displayed at the bottom of the chat pane) include new example prompts and a link to tips and tricks to improve your prompt skills.

About security, privacy and AI

Copilot is built on Microsoft's comprehensive approach to enterprise security, privacy, compliance, and responsible AI. Our philosophy is that your data is your data: customer data in Business Central is not used to train AI models.

Read the FAQ for Copilot data security and privacy for Dynamics 365 and Power Platform.

Try it out

Copilot is available exclusively for Business Central online.

To experience Chat, sign in to your Business Central environment and find the Copilot icon in the app bar at the top.

Customers upgrading their environment may need to first enable Chat with Copilot from the Feature Management page.

Prior to this release wave, if a method in a system module was instrumented with telemetry, any call from AL to the method wouldn’t be sent as a telemetry event to the app publisher’s telemetry pipeline.

This condition has now changed. A telemetry event from the system module (as long as Scope == All) is sent to the Application Insights resource defined in the app.json manifest of the calling app/extension. This capability is particularly beneficial for the Copilot system module.

About security, privacy, and AI

Copilot is built on Microsoft's comprehensive approach to enterprise security, privacy, compliance, and responsible AI. Our philosophy is that your data is your data: customer data in Business Central is not used to train AI models.

Read the FAQ for Copilot data security and privacy for Dynamics 365 and Power Platform.

Join our Copilot and AI discussions

We're excited to have you with us on our Copilot journey. Join the partner discussion on the Dynamics 365 Business Central Partner Community Network on Viva Engage (formerly Yammer) to help us shape the future of AI in Business Central.

You can now use Copilot prompt actions on Card, Document, and ListPlus page types to nudge users to use your Copilots on such pages. The required AL code follows the same model as when adding Copilot prompt actions to list pages.

As an example, this code adds four prompt actions to the Customer Card via a page extension, where two of the Copilot prompt actions are nested in a group.

pageextension 50110 "Customer with prompt" extends "Customer Card" {     actions     {         addlast(Prompting)         {             action(DraftWithCopilot)             {                 Caption = 'Draft with Copilot';                 Ellipsis = true;                 trigger OnAction()                 begin                     Message('Draft with Copilot pressed');                 end;             }             action(OpenModal)             {                 Caption = 'Open Modal';                 Ellipsis = true;                 trigger OnAction()                 begin                     RunModal(22);                 end;             }             group(PromptGroup)             {                 action(PromptAction1)                 {                     trigger OnAction()                     begin                         Message('PromptAction1 pressed');                     end;                 }                 action(PromptAction2)                 {                     trigger OnAction()                     begin                         Message('PromptAction2 pressed');                     end;                 }             }         }     } } 

The example results in the user experience on the customer card shown in the following image.

The base application already uses Copilot prompt actions on cards—for example, on the Bank Reconciliation card where it provides multiple Copilot actions.

This feature integrates Copilot in Power Automate with Business Central so that you can start creating automation flows based on natural language. When such flows are opened in Power Automate for further refinement, you can take advantage of the Copilot experience in Power Automate.

Copilot in Power Automate allows open-ended and conversational experiences while authoring flows that use your Business Central data. You can ask questions and get assistance to improve and change those flows. Copilot stays with you in your flow and helps you build, set up, and run an automation on your behalf through a comfortable chat experience. Copilot takes your input and provides either documentation, links, or answers in the Copilot chat pane. But most importantly, it makes changes to the structure of the flow based on your natural language description.

This feature helps you streamline business processes and improve productivity by shortening the path to automation.

Customers with environments deployed to the United States, United Kingdom, India, and Australia Azure regions continue to benefit from Microsoft Azure OpenAI Service availability in their own geography with no administrative setup for Microsoft Copilot in Business Central.

For all other geographies, the administrative setting on the Copilot & AI Capabilities page is now on by default.

• New environments of version 25.0 or later no longer require administrative setup, and users are immediately able to enjoy Copilot capabilities.
• Environments upgrading to version 25.0 in 2024 release wave 2 are automatically updated. The Allow data movement setting in the Copilot & AI Capabilities page is switched on, and users will be able to access Copilot capabilities as soon as the environment is upgraded.
• Administrators can use this switch at any time to opt out of data movement across geographies, which deactivates Copilot for all users of that environment.

Looking for more details?

FAQ for Copilot data security and privacy for Dynamics 365 and Power Platform

Copilot data movement across geographies

For greenhouse gas emissions (GHG), Copilot can estimate total emissions based on descriptions and input parameters and adjust emission factors for future use.

To try out this feature:

1. Sign in to your Business Central online environment.
2. Go to the Sustainability Journal page.
3. Enter Sustainability accounts and fill in the Descriptions field with accurate information as well as other inbound parameters, such as Fuel/Electricity, Distance, Custom Amount, Installation Multiplier, or Time Factor.
4. Choose Suggest emissions with Copilot.

Join the conversation

We're excited to have you with us on our Copilot journey.

Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the forum at aka.ms/bcIdeas, or join the partner community discussion on the Dynamics 365 Business Central Partner Community Network on Viva Engage (formerly Yammer) to help us shape the future of AI in Business Central.

Copilot can help you create and update number series faster on the No. Series page. The Generate action opens the Generate No. Series with Copilot dialog, where you can enter a prompt to create new, or modify existing, number series.

Number series setup creation

To help you write the prompt, the Create new action in the Generate No. Series with Copilot dialog provides sets of prompt guides that you can use as inspiration.

When you choose Generate, Copilot creates proposals for one or more number series, and you can review the proposals in the No. Series Proposals view. You can remove the proposals that you don't like, and edit the ones you do. When you're ready, you can choose Keep it to add or update a proposal. In addition, Copilot updates various setup pages with the number series you decided to keep.

Number series updates

In the Generate No. Series with Copilot dialog, Modify existing offers sets of prompt guides to help you write a prompt to update an existing number series.

When you choose Generate, Copilot updates one or more number series proposals, and you can review the proposals in the No. Series proposals view. You can remove the proposals Copilot generated, and edit the ones you like. When you're ready, you can choose Keep it to add or update a proposal.

About security, privacy, and AI

Copilot is built on Microsoft's comprehensive approach to enterprise security, privacy, compliance, and responsible AI. Our philosophy is that your data is your data: customer data in Business Central is not used to train AI models.

Read the FAQ for Copilot data security and privacy for Dynamics 365 and Power Platform.

Summarize is a new capability of Copilot in Business Central:

• A new summary FactBox displays on card and document pages, such as a Customer, Sales Order, Item, and even your custom pages.
• Get summaries of the record by displaying a few bullet points that are the top things you need to know, with even more insights available on demand.
• Copilot searches through data from the current page, from FactBoxes, and from related pages and statistics to identify what is urgent and important, so you don't have to.
• Summaries are tailored to your role, focusing on what matters to you.
• Interact with the summary to navigate, explore, and quickly act on your data.
• Refresh the summary based on the latest data.

Try it out

Look for the Summary FactBox on your pages and expand to get started.

Use the links to scroll to the field or navigate to the page that has more detail.

Show more insights in the Copilot pane, where you can ask follow-up questions to find records, analyze your data, or learn how to act in Business Central.

About security, privacy, and AI

Copilot is built on Microsoft's comprehensive approach to enterprise security, privacy, compliance, and responsible AI. Our philosophy is that your data is your data: customer data in Business Central is not used to train AI models.

For more information, go to FAQ for Copilot data security and privacy for Dynamics 365.

Join the discussion

We're excited to have you with us on our Copilot journey.

Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the forum at aka.ms/bcIdeas, or join the partner community discussion on the Dynamics 365 Business Central Partner Community Network on Viva Engage (formerly Yammer) to help us shape the future of AI in Business Central.