Microsoft Power Platform Integration with Business Central

PREVIEW: This feature is in preview.

Important

This functionality requires version 17 or later of Business Central online while service update 189 is required for Microsoft Dataverse. The release information for Microsoft Dataverse is published on the latest version availability page.

Business Central Virtual table, which is published on AppSource, is a virtual data source in Microsoft Dataverse, and enables create, read, update, delete (CRUD) operations from Microsoft Dataverse and Microsoft Power Platform. By definition, the data for virtual tables does not reside in Microsoft Dataverse. Instead, it continues to reside in Business Central. To enable operations on Business Central tables in Microsoft Dataverse, tables must be made available as virtual tables in Microsoft Dataverse.

Prerequisite reading

To work with Business Central virtual tables, you must understand how Microsoft Dataverse and virtual tables work. Therefore, the following documentation is a prerequisite:

Virtual tables for Business Central

Open Data Protocol (OData) APIs exposed through API Pages in Business Central can be consumed in Microsoft Dataverse and virtual tables can be generated. Virtual tables in Microsoft Dataverse acts as regular tables and therefore also in Power Platform. Makers can now build experiences in customer engagement apps with data directly from Business Central with full CRUD capability and without copying to Microsoft Dataverse, and leverage all the logic already residing in Business Central.

Using Custom APIs as basis for virtual tables

Since the virtual tables depend on APIs exposed on Business Central, custom APIs can also used for generating virtual tables. For more information, see Developing a Custom API.

Known limitations

There are known limitations with Business Central virtual tables including:

  • Flows are not triggered for virtual tables. Currently, Business Central has no way to signal Microsoft Dataverse about data change events.
  • Virtual tables cannot be used in Charts. Microsoft Dataverses does not support virtual tables being using in Charts.
  • Virtual tables cannot be customized on Microsoft Dataverse, for example, adding new columns. All modifications to virtual tables must happen in the API exposed on Business Central. But custom APIs can be developed and consumed as virtual tables.
  • Attachment and Images/Pictures are not supported for virtual tables.
  • BLOB to multiline support is not supported in the preview.
  • Advanced search has some limitations. Each query designed translates to an OData query against Business Central.
    • The following predicates are not supported: Does Not Equal, Does Not Contain, Does Not Begin With, Does Not End With, Does Not Contain Data, and Contains Data.
    • Combining And and Or groups across columns.
    • Filtering on related tables.
  • PowerApp Portals are not supported with Virtual Tables in current preview.

See Also

Table Modeling
Application Lifecycle Management for Solutions that use Virtual tables
Business Central and Microsoft Dataverse Admin Reference
FAQ
Developing a Custom API