- Feature
- Faster data loading with improved table extension data model
- Availability
- Generally available (October 2026)
- Industry focus
- Maintenance, repair and operations (MRO) and spare parts distribution
MRO and spare parts distributors rarely run a plain ERP. They add fields for manufacturer part numbers, cross-references, criticality ratings, shelf-life rules and customer-specific part codes. In Business Central, those fields live in table extensions. Business Central 29.0 changes how those extension fields are stored, and that has a direct effect on speed.
The industry challenge
A typical MRO distributor might have extensions that add fields to:
- Items (OEM part number, criticality, hazardous classification)
- Sales lines (customer asset reference, maintenance work order number)
- Customers (site codes, contract terms)
- Item ledger entries (batch and certification data)
Until now, Business Central stored extension fields in separate companion tables in the database. Every time the system read a record with extension fields, it had to join the base table with one or more companion tables. On large tables like items, sales lines and ledger entries, those joins add up, especially when several extensions extend the same table.
The more a business customized Business Central, the more it paid in performance.
What Microsoft delivered in Business Central 29.0
According to Microsoft, Business Central 29.0 introduces a new data model for table extensions. All fields on an AL table, both base and extension fields, are now stored in the same table in the database. Microsoft says this gives faster performance on all database operations that involve table extensions.
The same data model also allows developers to define indexes that combine base-table and extension fields, which is covered in a separate post in this series.
For customers, the important point is that this is a platform change. Existing extensions benefit without being rewritten.
Where the value shows up
| Business area | Impact for an MRO distributor |
|---|---|
| Page loading | Faster loading of item, customer and order pages with custom fields |
| Posting | Less overhead when posting documents that carry extension data |
| Reports and lookups | Quicker queries on large, customized tables |
| Customization strategy | Less performance penalty for extending the system |
| Development | Opens the door to indexes that mix base and extension fields |
The strategic point is that customization becomes cheaper in performance terms. Distributors can extend Business Central to fit their business with less worry about slowing it down.
A worked scenario
Consider a distributor of industrial spare parts serving manufacturing plants and utilities (an illustrative example). It runs three extensions that add more than 40 fields to the item table, plus fields on sales lines and customers.
Sales staff often search items by OEM part number and open item cards to check criticality and alternative parts. Before 29.0, those pages felt slow, especially at busy times. After the 29.0 update, the extension fields are stored alongside the standard fields, and item searches and order entry feel noticeably quicker. No extension needed rewriting. The IT manager confirms the change with before-and-after page load measurements.
Adoption considerations
- Measure before and after. Record page load and posting times so you can see the benefit.
- Check app compatibility. Make sure all extensions are compatible with version 29.0 before updating.
- Watch database size limits. Your partner may want to review very wide tables with many extension fields.
- Revisit old workarounds. Some performance workarounds for extension fields may no longer be needed.
- Plan new indexes. Consider mixed-field indexes for your most frequent searches.
The bottom line
MRO and spare parts distributors rely on customized data to serve customers quickly and accurately. The new table extension data model in Business Central 29.0 removes much of the performance cost of that customization. It's an invisible change with very visible results: faster pages, quicker posting and room to keep extending the system.
If your Business Central system is heavily customized, it's worth reviewing performance and index opportunities after the 29.0 update with an experienced adviser.
Sources: Microsoft roadmap 573332 · Microsoft roadmap 573315