- Feature
- Map new Dataverse fields in Business Central
- Availability
- Generally available (October 2026)
- Industry focus
- Wholesale distribution
In wholesale distribution, the commercial team and the back office rarely move at the same speed. Sales leaders want to capture a new customer attribute this quarter. Finance and operations need it to reach the ERP in time to drive pricing, credit and fulfilment. Business Central 29.0 removes one of the most common blockers between those two worlds.
The industry challenge
Distributors that pair Dynamics 365 Sales with Business Central usually sync accounts, contacts, items and prices through Dataverse. That integration works well until the business changes its mind about what data matters.
Typical requests come from the sales floor:
- A "buying group" or "co-op membership" flag that determines rebate eligibility
- A preferred delivery window that the warehouse needs to plan routes
- A customer segment that decides which price list applies
- A compliance attribute, such as a hazardous-goods licence number
Until now, getting a new custom Dataverse column into Business Central meant creating or changing a per-tenant extension (PTE) in the integration layer. That is a development task. It needs a partner or in-house AL developer, a test cycle and a deployment window. In practice, many distributors simply didn't bother. Fields lived in CRM only, and someone re-keyed the information into the ERP or kept it in a spreadsheet.
What Microsoft delivered in Business Central 29.0
Microsoft has moved this work from code to configuration. When a new field appears in Dataverse, an administrator can now work entirely from the Integration Table Mappings page:
- Refresh the list of Dataverse fields.
- Add the new field to an existing table mapping.
- Pick the matching Business Central field.
- Set the synchronization direction.
- Enable it, and the field takes part in sync from then on.
No table extension is created or modified, and the existing mapping doesn't need to be rebuilt. Microsoft positions the feature for organizations that customize their Dataverse environments often, which describes most growing distributors.
Where the value shows up
| Business area | Before 29.0 | With 29.0 |
|---|---|---|
| Change lead time | A development ticket, testing and deployment of an extension | An administrator configures the mapping on the same day |
| Cost of change | Partner or developer hours for each new field | Administrator time only |
| Data quality | Re-keying between CRM and ERP, or spreadsheets on the side | One field, synchronized in a defined direction |
| Upgrade risk | Another extension to maintain through each major update | No extra extension in the integration layer |
| Sales and finance alignment | Sales ideas stall in the backlog | Commercial attributes reach pricing, credit and fulfilment quickly |
The most important benefit is speed of response. Distribution margins depend on reacting to supplier programs, customer contracts and market shifts. If a new rebate program depends on a customer attribute, every week of delay is a week of manual workarounds or missed claims.
A worked scenario
Consider a regional food-service distributor (an illustrative example). Its sales team joins a purchasing consortium, and customers who belong to that consortium get a different freight policy and a quarterly rebate. The CRM team adds a "Consortium member" column on the account in Dynamics 365 Sales.
In the old model, the finance manager raises a ticket with the partner. Two or three weeks later, after an extension update, the field appears on the Business Central customer card. Meanwhile, the credit controller keeps a list in Excel and the warehouse applies the wrong freight terms to some orders.
With Business Central 29.0, the system administrator refreshes the Dataverse field list that afternoon. They map the column to a customer field, set sync to run from Dataverse to Business Central, and enable it. From the next sync, finance can filter customers by consortium membership, apply the right freight rule and prepare rebate claims from real data.
Adoption considerations
- You still need a target field. The feature maps a Dataverse column to a Business Central field. If the right field doesn't exist in Business Central yet, that is still a design decision.
- Decide ownership of each field. Choose the sync direction deliberately. As a rule, the system where the data is created should be the master.
- Govern the change. Faster change is good, but keep a simple log of which fields were mapped, why and by whom. That protects audit trails and reporting.
- Review older extensions. Some existing integration PTEs may only exist to expose custom fields. Those are candidates to retire at the next upgrade.
- Test in a sandbox first. Bidirectional sync on a field that both teams edit can create conflicts.
The bottom line
For distributors, the gap between a commercial decision and an operational result is where margin leaks out. Dataverse field mapping in Business Central 29.0 is a small administrative change with a large effect. It shortens that gap from weeks to hours and removes a recurring development cost. Organizations that customize their CRM often will feel the difference first.
If you are planning how to bring CRM and ERP data closer together, it is worth reviewing your current integration extensions with an experienced Business Central adviser.
Source: Microsoft roadmap 573365