See a collection of features designed for a particular role, and learn how to get to other features in the application.

Dynamics 365 Business Central is an all-in-one business management application . Upgrade your legacy ERP system or accounting software to a comprehensive solution to seamlessly manage your finances, operations, sales, and customer services.

Twice a year, Microsoft releases feature updates for Dynamics 365 Business Central. The first update is in February and the second one is in October. Microsoft has named these updates as release waves – 1, 2, 3, and so on. These updates both improve BC’s features and enhance its performance, to help users be more productive and more efficient.

How to implement Business Central in my business?

It’s easy contacting us to or schedule a meeting to assess your current ERP system, and business operations, challenges and future needs to assess how well whether Business Central fits.

The “Wave 2” of the annual release plan for Dynamics 365 Business Central version 19 product launch is planned for October. Microsoft has publicly announced new features spanning from the platform’s expansions to new countries to new onboarding features and to the application and development features. (………. details listed here are subject to change).

 Dynamics 365 Business Central availability in new countries

 Starting from the 2021 Wave 2 release, Dynamics 365 Business Central will be available in the following new countries:

• Argentina
• Bulgaria
• Chile
• Myanmar
• Puerto Rico
• Slovakia
• Ukraine

These new availabilities are achieved through partner-led localizations available on AppSource + built-in language module.

New features on the Application layer

Both Finance and Supply Chain areas will receive improvements on

. Availability of more fields on different entities for customizing pages via personalization (directly by the end-user).:

• The availability of fields related to Vendor information’s on the Get Receipt Lines page or information related to customer’s orders on the Get Shipment Lines.

• The Bank Accounts page now displays the Balance at Date and Balance at Date (LCY).
• General Journals and Recurring General Journals can now display the External Document No.
• Information about weights and volume are available in all sales documents and purchase documents (you can add the Unit Gross Weight, Unit Net Weight, Unit Volume, and Units per Parcel via personalization).

• Add the Expected Receipt Date field to the Purchase Quotes, Purchase Quote Archives, and Purchase Orders pages.
• Job-related columns can be added to all purchase documents.
• Add the Transfer Order Receipt and Shipment Quantities fields to the Item Card page.
• Add the Description 2 field to all sales, service, purchase drafts, and posted and archived document lines.
• Add the Source Type and Source No. fields to the General Ledger Entries page for better analysis.

Use requisition and planning worksheets to enter plans ofwhat you need to order and then create the orders for both physical inventory items and non-inventory items (such as services) to have a unified process.

Non-inventory items will support locations, and the location information will be copied in the item ledger, values, and job ledger entries records. You will be able to perform statistics for the location, also for services.

The Payment Reconciliation Journal will be improved with the following capabilities:

• Separate number series
• Posting preview
• Ability to reverse the G/L register posted through the journal

The Bank Reconciliation page will be improved with the following capabilities:

• Bank ledger entries are now filtered, so only ledger entries after the statement’s ending date are displayed.
• When applying auto-matching, the user can decide not to overwrite any of the already matched entries or to overwrite all.
• Many-to-1 matching is now possible, so many bank statement lines can be matched against one bank ledger entry.
• When you transfer differences to be posted in a general journal, the entries will be auto-matched when you return to the bank reconciliation, reducing the redundant manual step.

Production processes like planning worksheets, order planning, capable-to-promise can now use information about bills of materials and routes defined in the stock-keeping units (SKU).

You will be able to specify a rounding precision for the base unit of measures to avoid rounding problems when using alternative units.

An alternative unit of measure for items can now be synched also with Dynamics 365 for Sales.

The new release will also remove the old sales documents reports (204..207) in favor of new sales document reports supporting Word Layout (1304..1307). You can ether use the new layouts (recommended) or clone the old layout to a custom layout and then continue using the cloned custom layout.

Data export to Excel. You will be able to export in excel lists embedded in a part on a page, such as Sales Lines on the Sales Order page or lists on a fact box pane. The Open in Excel action downloads a static copy of your list as an Excel file, applying your filters and sort order just as shown on the screen.

For reports, you can now select to export the report data to Excel on the request page. The Excel file will only include the raw data and not the report layout.

It will be useful for troubleshooting or data analysis. . Just go to the report’s request page and select the Send to menu. Here you have a new option now: Microsoft Excel Document (data only):

When you select this option, the report is rendered to include data only (data without the layout) and the raw dataset is presented in an Excel file. The Excel file contains the value of each field and the value of each variable and caption defined in the report. The exported dataset is the same dataset that is streamed to the reporting engine component of Business Central. When you have binary data inside the report, this is not exported into Excel (obviously) but it gives you an indication of the byte size. It works also for reportextension’s data.

Consider it as a “report inspector” for developers and consultants. Users must have the Allow Action Export Report Dataset To Excel permission assigned (you can assign the Troubleshooting Tools or Export Report Excel permission sets to them).

You can also export report data exported also as XML.

Integration with Dataverse, Dynamics 365, and Power Platform improvements

Dataverse integration. Use Integration Field Mapping to filter and choose the data to synchronize and how to couple records (this will avoid  writing extensions with custom business logic for synch).

Integration with Microsoft Teams, The Business Central web client will include a new action to share records to Microsoft Teams in the next release. This will allow you to type a message, choose recipients (team members, groups, or channels), and then send a message with a link to the Business Central record.

Power BI reports inside Business Central. In the next release, embed reports from any of your personal or shared Power BI workspaces (not only from the default workspace).

New features for IT Administrators

When using delegated admins,  create job queue entries and set those as ready to run with your delegated admin account. A licensed user from the customer can start the job queue entry to complete the process that the delegated admin created.

A partner, will be able to preload a list of recommended apps into the customer’s system (apps relevant for his business) to act as a “proxy” on AppSource. The customer can then install the preselected apps safely.

The administrator will have a new set of Automation APIs (in addition to the existing ones) that will permit the creation of user groups. New APIs for sharing files in Microsoft 365 will also be available for AL developers (these will permit sharing reports or other files using standard Microsoft 365 capabilities for cloud-based file sharing).

In the new release it is possible to use Azure Active Directory (Azure AD) groups to grant access to environments on a tenant . You will be able to associate an Azure AD group with an environment. The members of that Azure AD group will be synchronized to Dynamics 365 Business Central and granted access to that environment.

In the next release, you will be able to copy environments within and across different environment types, for example:

• Production to Production
• Sandbox to Sandbox
• Sandbox to Production

Also, new log signals related to the environment’s operations will be added to the Business Central operation logs.

It will also be possible to restart an environment from the Admin Center, for example, for troubleshooting purposes.

New features for AL developers

The AL compiler will be improved. When using code analyzers, you will  receive a warning on code compilation with additional URLs for documentation that links to the possible cause of the problem and possible solutions.

Another essential and top requested feature that you will see on version 19 is the ability to perform a force-sync on per-tenant extensions.

Breaking schema changes on SaaS are never permitted, but on version 19 (under the partner’s responsibility), you will be able to make breaking schema changes on PTEs. The new force sync schema change can be triggered via the Extension Management page or directly from the tenant’s Admin Center.

Please always remember that with this action, you will lose any data stored in your extension.

When debugging with Visual Studio Code, you will be able to capture the execution timing part of the snapshot from snapshot debugging. Using a new (and cool!) performance profiling editor in VS Code, you will be able to investigate how your code performs.

An important new feature is related to control the source access of your extension’s code. A property in the app.json file called ShowMyCode when enabled, permits debugging the extension and also to download source (PTE) and view code in symbols. This is  one of the main problems with debugging. (Many partners have ShowMyCode = false in their extensions, which makes debugging the extension’s code impossibile!f.)

Plans to add new options in the app.json file like AllowDebugSource, AllowDownloadSource, or AllowSymbolsSource to protect the source access effectively. This is when writing a “work in progress” project, and some details could change.

To improve performances of the NST, in the next release, whenyou’re using OData for integrations, you will be able to specify a read-only intent to use the read-only database replica (and then offloading the production database). You will also have a limit on the number of background sessions that you can start from the AL code.

Don’t forget to check for warnings in your code NOW because some of these (marked as v15 or v16) could become errors in the v19 release