Small and medium business | Business Central, N...

Add custom field to virtual table

(7) Share

Report

Posted on by DKaushik

Hi Community,

Summary : How to extend the virtual table to show custom fields in dataverse ? At the moment only limited fields are available in dataverse.

Detailed explanation :

Scenario - Vendors have power pages/portal access. They can see their orders. They want to provide a 'confirmation date' as an input on the sales order header (technically they want to edit order header).

Steps performed - Table extension created and field has been added on the business centrals sales order table.

Problem - As Sales order is a virtual table at the dataverse side, therefore I can not view the newly created field.

Thanks

All responses (5)

Answers (0)

Sort by

Suggested answer

YUN ZHU 103,103 Super User 2026 Season 2 on at

Like (5)

Report
Copy link

Link copied!

Hi, hope the following helps.

Business Central 2024 wave 1 (BC24): Add table and field mappings to existing integration tables (Dataverse)

https://yzhums.com/49260/

Dynamics 365 Business Central: Customizing an Integration with Microsoft Dataverse (Integrate custom tables)

https://yzhums.com/17065/

Thanks.

ZHU
Gerardo Rentería Ga... 27,621 Super User 2026 Season 2 on at

Like (3)

Report
Copy link

Link copied!

Hi

Here some more useful urls. I hope this can help you.

Dataverse - Discover Microsoft Business Central (bertverbeek.nl)

Best

GR
Suggested answer

Rishabh Kanaskar 6,231 Super User 2026 Season 1 on at

Like (6)

Report
Copy link

Link copied!

Hi,

Custom fields added through table extensions in Business Central do not automatically flow to Dataverse virtual tables. Only standard fields exposed by Microsoft are available. To surface your custom field, you need to use a custom API page in Business Central, publish it as a web service, and then integrate it into Dataverse (e.g., via virtual entities or Power Automate). Direct extension of virtual tables to include custom fields is not supported.

Thanks

Rishabh
Suggested answer

Jeffrey Bulanadi 9,128 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
Hi DKaushik,

Exposing custom fields from BC to Dataverse via virtual tables is a known limitation, especially when working with Power Pages or portal scenarios.

Here’s the cleanest path forward:

Virtual tables in Dataverse are metadata-bound: They only expose fields that are explicitly mapped in the connector metadata. Custom fields added via table extensions in BC are not automatically surfaced.

To expose your custom field (e.g., Confirmation Date), you’ll need to use the BC Virtual Table Metadata Synchronization Tool. This tool updates the Dataverse metadata to include new fields from extended tables.

Alternatively, you can use Dataverse Web API or Power Automate to surface the field indirectly:

Create a custom Dataverse table that mirrors the Sales Order header

Use Power Automate to sync the Confirmation Date from BC to this custom table

Expose the custom table in Power Pages for vendor input

This approach avoids modifying the virtual table directly and gives you full control over field visibility and access logic.

Helpful Reference
Power Automate integration with BC – Microsoft Learn
Dataverse Web API for BC – Microsoft Learn

If you find this helpful, feel free to mark this as the suggested or verified answer.

Cheers
Jeffrey
Suggested answer

Sumit Singh 11,805 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi DKaushik,

I think this query is too old (Aug 2024), may be already resolved by given answers.

Please let us know if still having any further question.