In the field mapping, several options are available to define how values are determined during the field mapping execution.

These field mapping options are split over three main processes. These main processes are always executed in this sequence:

  1. Get a value
  2. Modify a value
  3. Set a value
How the field mapping is executed, partially depends on the field type of the source field and the target field, as defined in the relevant document. A distinction is made between the field type String on the one hand and any of the other field types on the other.
Based on the field type, you can set up a field mapping in these ways:

  • Any to any: Usually, this is used to move data between D365 FO companies.
  • Any to string: Usually, this is used to export data or to move data to the staging journal.
  • String to any: Usually, this is used to import data directly or to the staging journal.
  • String to string: Can be used to export, import, or move data between D365 FO companies.

1. Get a value

The field mapping execution always starts with getting a value. Several options are available to get a value. Only one of these options is applied. These options are always checked in this sequence, and the first option found, is applied:

  1. Constant: The defined constant is the applicable value.
  2. Number sequence: The next available number in the defined number sequence is the applicable value. 
  3. Display method: The defined display method is used to get the applicable value.
  4. Dimension set: Only if the source field type is int64, the 'Get a value' process gets the financial dimension from the relevant financial dimension table.
  5. Ledger: Only if the source field type is int64, the 'Get a value' process gets the account number of ledger transactions based on the field option setup.
  6. Inventory dimension: Only if the source field type is int64, the 'Get a value' process gets the inventory dimension from the inventory dimension setup.
  7. Source field value: If none of the previous options is set up, the source field value is the applicable value.
Example: If both a display method and an inventory dimension are set up, only the display method is executed.

2. Modify a value

Several options are available to modify a value. All these options can be applied in one field mapping. These options are always applied in this sequence:

  1. Transformation and type conversion. In which sequence and if the transformation and type conversion are applied, depends on the source field type and the target field type:
    • Any to any: Only the transformation is applied.
    • Any to string: The type conversion is applied before the transformation.
    • String to any: The transformation is applied before the type conversion.
    • String to string: The type conversion is applied before the transformation.
  2. Custom: A custom expression modifies the value.
  3. External reference: The output value of this option depends on the direction:
    • On export, the external ID or revision that is linked to the D365 FO RecId is the output value.
    • On import, the D365 FO RecId, that is linked to the external ID or revision is the output value.
  4. Lookup: A lookup gets a value from another table and uses it as the output value of this option.

Note:

  • The output of the 'Get a value' process is the input for the 'Modify a value' process.
  • In the 'Modify a value' process, the output value of the previous option is the input value for the next option.

Example: If both a transformation and a lookup are set up, both are applied. The transformed value is the input for the lookup.

3. Set a value

The field mapping execution always ends with setting the target field value. Several options are available to set this value. Only one of these options is applied. These options are always checked in this sequence, and the first option found, is applied:

  1. Edit method: An edit method sets the target field value. On import, the edit method changes the value in the target field of the D365 FO table.
  2. Inventory dimension: Only if the target field type is not String, the 'Set a value' process sets the inventory dimension in the inventory dimension table.
  3. Dimension set: Only if the source field type is not String, the 'Set a value' process sets the financial dimension in the relevant financial dimension table.
  4. Ledger: Only if the source field type is not String, the 'Set a value' process sets the account number of ledger transactions based on the field option setup.
  5. Set target field value: If none of the previous options is set up, the output of the 'Modify a value' process is set as the target field value.

Note: The output of the 'Modify a value' process is the input for the 'Set a value' process.

Example: If both an inventory dimension and ledger are set up, only the inventory dimension is applied.

Provide feedback