Multi Entity Management
ID fields in the 8000 fieldnumber range
Section titled “ID fields in the 8000 fieldnumber range”Version: August 2026 / Multi Entity Management 8.8.x / Business Central 28.x
1. Preamble
Section titled “1. Preamble”What are the ID fields in the 8000 field number range?
Fields in the 8000 field number range, such as:
- Currency Id
- Customer Id
- Vendor Id
- Item Id
are legacy integration identifier fields used by older synchronization frameworks, CRM integrations, and external applications in Microsoft Dynamics NAV and earlier Business Central versions.
These fields were originally introduced to provide technical identifiers for records before the SystemId field became the platform standard.
2. Are these fields being replaced by SystemId?
Section titled “2. Are these fields being replaced by SystemId?”Yes. In modern versions of Business Central, Microsoft is increasingly standardizing on the SystemId field (Field No. 2000000000) as the primary technical identifier for records.
SystemId is now the preferred identifier because it:
- exists on all tables,
- is immutable after creation,
- is globally unique (GUID-based),
- is used consistently by Business Central APIs,
- supports modern cloud and cross-environment integrations,
- simplifies synchronization scenarios.
As a result, the legacy ID fields in the 8000 range are gradually becoming less relevant in newer integration architectures.
3. Recommendation for Multi Entity Management
Section titled “3. Recommendation for Multi Entity Management”It is recommended to:
- Activate “Transfer at Insert” for the SystemId field (2000000000).
- Deactivate both:
- “Transfer at Insert”
- “Transfer at Modify” for legacy ID fields in the 8000 field number range.
This ensures:
- consistent record identity across environments and companies,
- alignment with Microsoft’s modern integration model,
- reduced dependency on legacy integration fields,
- improved API and synchronization consistency.
4. How should existing 8000-range ID fields be handled?
Section titled “4. How should existing 8000-range ID fields be handled?”These fields should generally be treated as legacy integration fields:
- preserve existing values when required for backward compatibility,
- avoid manually changing values,
- avoid using them as the primary synchronization identifier in new implementations.
For modern integrations and replication scenarios, SystemId should be considered the authoritative technical identifier for records.