Field Mapping
Business Central Field Mapping
Section titled “Business Central Field Mapping”This reference shows how Microsoft Dynamics 365 Business Central entities map to the N’entropy EUDR platform.
Vendor → Supplier Mapping
Section titled “Vendor → Supplier Mapping”| BC Field | Platform Field | Notes |
|---|---|---|
id | externalId | Unique BC identifier |
displayName | name | Vendor display name |
addressLine1 | address | Primary address |
city | city | City |
state | state | State/province |
country | country | Country code (ISO 3166) |
postalCode | postalCode | Postal/ZIP code |
email | email | Contact email |
phoneNumber | phone | Phone number |
website | website | Company website |
taxRegistrationNumber | taxId | Tax/VAT number |
lastModifiedDateTime | lastSyncedAt | Last modification timestamp |
Example BC Vendor Response
Section titled “Example BC Vendor Response”{ "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890", "number": "V10000", "displayName": "Amazon Timber Co.", "addressLine1": "123 Forest Road", "addressLine2": "", "city": "Manaus", "state": "Amazonas", "country": "BR", "postalCode": "69000-000", "phoneNumber": "+55-92-1234-5678", "email": "contact@amazontimber.co", "website": "https://amazontimber.co", "taxRegistrationNumber": "12.345.678/0001-90", "lastModifiedDateTime": "2024-06-15T10:30:00Z"}Mapped Platform Supplier
Section titled “Mapped Platform Supplier”{ "externalId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890", "externalSystem": "dynamics_bc", "name": "Amazon Timber Co.", "address": "123 Forest Road", "city": "Manaus", "state": "Amazonas", "country": "BR", "postalCode": "69000-000", "email": "contact@amazontimber.co", "phone": "+55-92-1234-5678", "website": "https://amazontimber.co", "taxId": "12.345.678/0001-90", "syncStatus": "synced", "lastSyncedAt": "2024-06-15T10:30:00Z"}Item → Product Mapping
Section titled “Item → Product Mapping”| BC Field | Platform Field | Notes |
|---|---|---|
id | externalId | Unique BC identifier |
displayName | name | Item display name |
number | hsCode | Item number (may need custom mapping) |
type | — | BC item type (Inventory, Service, etc.) |
itemCategoryCode | category | Category classification |
unitOfMeasure.code | — | Unit of measure |
lastModifiedDateTime | lastSyncedAt | Last modification timestamp |
Example BC Item Response
Section titled “Example BC Item Response”{ "id": "b2c3d4e5-f6a7-8901-bcde-f12345678901", "number": "ITEM-1001", "displayName": "Brazilian Hardwood Planks", "type": "Inventory", "itemCategoryCode": "TIMBER", "unitOfMeasure": { "code": "KG", "displayName": "Kilogram" }, "lastModifiedDateTime": "2024-06-14T08:15:00Z"}Mapped Platform Product
Section titled “Mapped Platform Product”{ "externalId": "b2c3d4e5-f6a7-8901-bcde-f12345678901", "externalSystem": "dynamics_bc", "name": "Brazilian Hardwood Planks", "hsCode": "ITEM-1001", "syncStatus": "synced", "lastSyncedAt": "2024-06-14T08:15:00Z"}Custom Field Mappings
Section titled “Custom Field Mappings”You can override the default mapping for any entity type. Navigate to Integrations → Sync Config and define your mappings:
{ "suppliers": { "displayName": "name", "addressLine1": "address", "city": "city", "country": "country", "taxRegistrationNumber": "taxId", "customField_EUDR_Category": "eudrCategory" }, "products": { "displayName": "name", "number": "hsCode", "customField_Origin_Country": "originCountry" }}Custom Fields
Section titled “Custom Fields”If your BC instance has custom fields, you can map them by using the BC field name as the key:
{ "suppliers": { "EUDR_Country_of_Harvest": "originCountry", "EUDR_Commodity_Type": "commodityType" }}Custom fields must exist in the BC API response to be mapped. Contact your BC administrator to ensure custom fields are exposed via the API.
Unmapped Fields
Section titled “Unmapped Fields”Some platform fields don’t have direct BC equivalents and must be filled manually or via the REST API:
- Supplier:
isEUDRRelevant,products(relationship), geolocation data - Product:
description,commodityType, supplier association - Batch: Batches are not synced from BC (created manually or via REST API)
Data Type Handling
Section titled “Data Type Handling”| Type | Behavior |
|---|---|
string | Direct copy |
number | Parsed as float |
boolean | Parsed from true/false/0/1 |
date/datetime | Parsed as ISO 8601 |
null/undefined | Skipped (existing value preserved) |