Doc Summary 
Swedish Business Central view name: Sync Data Fields
Field Mappings define how each field is synchronized between the Subsidiary company and the Central company in Easy Connect.
This configuration determines:
- which fields participate in synchronization
- which direction data should flow
- whether a field should be replaced with a fixed value
- whether certain fields are mandatory
- the order in which values are validated
Field Mapping Overview #
You access the mapping from:
Easy Connect Setup → Actions → Field Mappings
Each row represents a field in a Business Central table that Easy Connect can synchronize.
Mappings work on a per-table, per-field basis.
Only fields with OnField Validate = enabled are processed during synchronization.
Field Descriptions #
Below is a complete explanation of each field in the mapping table.
Company & Field Identification #
| Field | Description |
|---|---|
| Subsidiary Company Name | The subsidiary company configured in Easy Connect Setup. Visible only when the setup links multiple subsidiaries. |
| Table Name | The Business Central table where the field exists (e.g., Sales Header, Sales Line). |
| Field No. | Internal field number in the table. |
| Field Caption | The readable name of the field (e.g., Sell-to Customer No.). |
Synchronization & Validation Logic #
| Field | Description |
|---|---|
| OnField Validate | Must be enabled for the field to be included in synchronization. If OFF → Easy Connect ignores this field entirely. |
| Subsidiary Field Mandatory (SO) | Indicates the field is required on Sales Orders in the subsidiary company. |
| Subsidiary Field Mandatory (RO) | Indicates the field is required on Return Orders in the subsidiary company. |
| Condition Code | Optional condition that controls when the field should be applied. Uses the same condition logic as Web Connect. |
| Validation Order | Determines processing order when multiple fields in the same table must be validated in sequence. 0 = standard order. |
Value Substitution & Overrides #
| Field | Description | Common for |
|---|---|---|
| Substitute Value Type | Specifies how the replacement value should be determined. Options: Fixed Text or Field Value. | All setups needing overrides |
| Substitute Value | The actual value to use instead of the source field value. | Common for pricing, customer no., posting groups |
Example:
If a Sales Order in the Subsidiary always must use customer number IC-AS in the Central company:
- Substitute Value Type = Fixed Text
- Substitute Value = IC-AS
This means:
The customer number from the Subsidiary is ignored.
The order in Central always uses customer IC-AS.
Direction Control (One-way vs Two-way Sync) #
(Insert screenshot here of Active toggle fields)
| Field | Description | Common for |
|---|---|---|
| Active – Subsidiary → Central | Enables synchronization from Subsidiary to Central. Typically ON for most fields. | All |
| Active – Central → Subsidiary | Enables synchronization from Central to Subsidiary. Normally OFF except special cases. | Tracking numbers |
Typical usage #
- Subsidiary → Central:
- Sell-to Customer No.
- Item No.
- Quantities
- Dimensions
- Line descriptions
- Central → Subsidiary:
- Tracking numbers (godsupplysningsnummer)
- Shipment information
- Warehouse status
Most fields are not returned from Central unless explicitly required.
How Synchronization Works #
Step 1 — Subsidiary updates or creates a document #
Fields marked with Active – Subsidiary → Central are evaluated.
Step 2 — Easy Connect checks ‘OnField Validate’ #
If OFF → field is skipped.
If ON → field participates.
Step 3 — Conditions are evaluated #
If a Condition Code is specified, the mapping only applies when the condition is true.
Step 4 — Substitute logic runs (if configured) #
Examples:
| Scenario | Result |
|---|---|
| Substitute Value Type = Fixed Text | Always uses the fixed value (e.g., customer IC-AS) |
| Substitute Value Type = Field Value | Uses another field as the source |
Step 5 — Data is written to the receiving company #
Direction is determined per field:
- Subsidiary → Central
- Central → Subsidiary
- Both
Practical Example #
A sales order in the Subsidiary has customer 50000.
Field mapping in Easy Connect says:
- Substitute Type: Fixed Text
- Substitute Value: IC-AS
- Active Subsidiary → Central: ON
- OnField Validate: ON
Result:
The order created in the Central company always uses IC-AS, regardless of the original customer number.
Best Practices #
- Only enable Active – Central → Subsidiary for fields that must return (e.g., tracking numbers).
- Always set Validation Order when multiple related fields must process in sequence.
- Use Substitute Value to maintain consistent internal customer numbers, dimensions, or posting groups.
- Keep field mappings as simple as possible — avoid unnecessary two-way sync.
- For conditional logic, reuse Condition Codes for consistent behaviour.
Related Docs #
- Easy Connect Order Synchronization LÄNK
- Easy Connect Master Data Sync LÄNK
- Easy Connect Sync Log LÄNK
- Easy Connect Companies LÄNK
- Easy Connect FAQ LÄNK