1. To-Increase Dynamics 365 for Finance & Operations
  2. EDI studio
  3. Flows

Define field options
Activity Flow

For each field mapping, you can set additional field options. Each field option has specific properties. If you select a field option, also fill in the related properties.

Application Consultant Application Consultant Start Start Apply number sequence Apply number sequence You can use a number sequence to get the field value. So, instead of the source field value, the next available number in the number sequence is the applicable value. Procedure 1. Click Connectivity studio Integration Design. 2. On the Message tab, in the list, find and select the desired message. 3. Click Edit. 4. In the Mapping section, in the Target record pane, in the list, find and select the desired target record. 5. On the Mapping tab, on the Field mapping tab, in the list, find and select the desired field mapping. 6. Click the Field options tab. 7. Select the Number Sequence check box. 8. In the Number sequence code field, enter or select a value. 9. Close the page. Apply display method Apply display method You can use a display method to get the applicable value. For example, you can use a display method to calculate a value. Procedure 1. Click Connectivity studio Integration Design. 2. On the Message tab, in the list, find and select the desired message. 3. Click Edit. 4. In the Mapping section, in the Target record pane, in the list, find and select the desired target record. 5. On the Mapping tab, on the Field mapping tab, in the list, find and select the desired field mapping. 6. Click the Field options tab. 7. Select the Display method check box. 8. Define if you want to use a display method from the: - Table: You can select a display method that is defined for the source record table. - Entity: You can select a display method that is defined for the entity of the source record table. In the Method location field, select an option. Note: You can add a custom display method to the table entity instead of the table to avoid code changes to a standard D365 FO table. 9. In the Display method field, enter or select a value. Note: By default, no display methods are available for the 'BisBufferTable'. 10. Close the page. Apply custom handler Apply custom handler You can use a handler class to set the target field value. Several handler classes are available. For example, to get the current date, to add the time to a date, or to get the current company. Procedure 1. Click Connectivity studio Integration Design. 2. On the Message tab, in the list, find and select the desired message. 3. Click Edit. 4. In the Mapping section, in the Target record pane, in the list, find and select the desired target record. 5. On the Mapping tab, on the Field mapping tab, in the list, find and select the desired field mapping. 6. Click the Field options tab. 7. Select the Custom check box. 8. In the Handler field, enter or select a value. Note: You can develop a custom handler class. This must be derived from the 'BisMappingCustomMethod' class. 9. In the Type conversions field, enter or select a value. 10. Close the page. Apply custom expression Apply custom expression You can use an expression to modify the value. In the expression, use source fields, target fields, or mapping variables as variables. As a variable in the expression, you can use a: Field from any record of the applicable document. If you use a field from another record than the current record, make sure this record is mapped before the current record. Mapping variable that is defined for the message. Examples: You can use an expression to: Combine two fields. You can, for example, make a contact location name specific by combining it with the purpose. The expression can be: Description+'-'+Purpose. This results in, for example: Shop Main Street-Financial. Calculate the unit price based on the quantity and line amount on a purchase order confirmation. The variables are from the source record: Qty (PurchLine, PurchQty field) and Amount (PurchLine, LineAmount field). The expression is: Amount/Qty. Note:  Usually, you use string and real values as variables. Date calculations are not supported. For more information on expressions, refer to: Expression. Procedure 1. Click Connectivity studio Integration Design. 2. On the Message tab, in the list, find and select the desired message. 3. Click Edit. 4. In the Mapping section, in the Target record pane, in the list, find and select the desired target record. 5. On the Mapping tab, on the Field mapping tab, in the list, find and select the desired field mapping. 6. Click the Field options tab. 7. Select the Custom check box. 8. In the Variables pane, click New. 9. In the Variable field, type exactly the variable name as used in the expression. 10. In the Record origin field, select an option. 11. In the Record field, enter or select a value. 12. Define the document record field to which the variable is linked. In the Record field field, enter or select a value. Note: The field type, as defined for the document record field, is shown as well. 13. During a message run, you can use mapping variables to temporary store values. You can write (calculated) values to a mapping variable. Later, during the same message run, you read the value from the mapping variable for use in a custom expression. In the Mapping variable field, enter or select the mapping variable which value is used in the expression. Note: Make sure, the field mapping in which the mapping variable is written, is done before the field mapping for which you define the custom expression. 14. In the Variable type field, select an option. 15. In the Language field, enter or select a value. 16. In the Expression field, enter the expression, using variables. 17. Before the output value of the custom option is determined, you can apply a type conversion to the value that is returned by the custom expression. In the Type conversions field, enter or select a value. Note: You can test the created expression. To do so, click test expression. On the dialog, fill in the values of the variables and click Execute. 18. Close the page. Notes Applying expression conditions can influence the message performance. So, only apply an expression condition if required and keep it as simple as possible.An example of a more complex custom expression. Based on the values of the 'netPrice' from the source record and the 'taxPerc' from the target record, the tax amount is calculated. Apply lookup Apply lookup You can use a lookup to get a value from another table and use it as the output value of this option. For example, you can get a value from a table that is not in the source document.The other table must have the source field as the single key field. The current value of the 'Modify a value' process is the input of the lookup. As a result, the value that is returned by the lookup is the value of the Return value field.Before determining the output value of this option, you can apply a type conversion or a transformation. Procedure 1. Click Connectivity studio Integration Design. 2. On the Message tab, in the list, find and select the desired message. 3. Click Edit. 4. In the Mapping section, in the Target record pane, in the list, find and select the desired target record. 5. On the Mapping tab, on the Field mapping tab, in the list, find and select the desired field mapping. 6. Click the Field options tab. 7. Select the Lookup check box. 8. In the Lookup table field, enter or select a value. 9. Define the key field of the table from which you want to get a value. In the Lookup key field field, enter or select a value. Note: This key field must be the same field as the source field of the current field mapping. 10. In the Return field value field, enter or select a value. 11. In the Type conversions field, enter or select a value. 12. In the Transformation field, enter or select a value. 13. Close the page. Apply external reference Apply external reference You can link an external ID to a record ID in D365 FO. Together with the external ID, you can also link an external revision number to a record ID.The application, as defined for the connector, is used to store the link between the reference table and record ID in D365 FO and the external ID and revision number.If you:Export data, the applicable external ID or revision is searched for in the target connector application. If a record exists for the reference table and the source field (RecId) combination, the external ID or revision of this record is as the output value of this option.Import data, the applicable target record ID is searched for in the source connector application. If a record exists for the combination of reference table and external ID and revision, the reference record ID of this record is the output value of this option. If no record exists for the combination, a record is created. The reference record ID of this record is the output value of this option.Note: You can only link an external ID or revision number to a record ID if, on the applicable document, the External reference field and the Revision field are filled in for the source field or target field of the current field mapping.You can only link a revision to a record ID in D365 FO if you also link the external ID. The external ID field mapping must precede the revision field mapping.Usually, you use the External reference option on a field mapping where the source field (export) or target field (import) is the RecID. Procedure 1. Click Connectivity studio Integration Design. 2. On the Message tab, in the list, find and select the desired message. 3. Click Edit. 4. In the Mapping section, in the Target record pane, in the list, find and select the desired target record. 5. On the Mapping tab, on the Field mapping tab, in the list, find and select the desired field mapping. 6. Click the Field options tab. 7. Select the External reference check box. 8. In the Type field, select an option. 9. In the Reference table field, enter or select a value. 10. Close the page. Apply edit method Apply edit method You can use an edit method to set the target field value. On import, the edit method changes the value in the target field of the D365 FO table. Procedure 1. Click Connectivity studio Integration Design. 2. On the Message tab, in the list, find and select the desired message. 3. Click Edit. 4. In the Mapping section, in the Target record pane, in the list, find and select the desired target record. 5. On the Mapping tab, on the Field mapping tab, in the list, find and select the desired field mapping. 6. Click the Field options tab. 7. Select the Edit method check box. 8. In the Method location field, select an option. 9. In the Edit method field, enter or select a value. Note: By default, no edit methods are available for the 'BisBufferTable'. 10. Close the page. Apply dimension set Apply dimension set On D365 FO tables, a financial dimension is expressed in a RecId to a financial dimensions table. So, it does not reflect the financial dimension name and value. You can use the Dimension set option to get or set the financial dimension value based on the RecId and the dimension name (or number) as defined for the field option. If the message is used to:Import, you receive the dimension value. Based on the RecId in the target field and the name (or number), the value is set in the relevant financial dimensions table. Note: On import, the target field type must be other than String.Export, based on the RecId in the source field and the name (or number), the dimension value is gotten from the relevant financial dimensions table. Note: On export, the source field type must be int64.Note:Only use the Dimension set field option if one of these fields is part of the field mapping:DefaultDimension: This field is used to store default dimensions for, for example, customers, vendors, or customer groups.LedgerDimension or OffsetLedgerDimension: These fields are used to store financial dimensions for ledger journals of the 'Main account' account type.DefaultDimension or OffsetDefaultDimension: These fields are used to store financial dimensions for ledger journals of other account types.This field must be the:Target field of the field mapping for imports.Source field of the field mapping for exports.For each financial dimension that you want to set or get, use a separate field mapping. So, in the field mapping, you can have the same financial dimension field several times. Procedure 1. Click Connectivity studio Integration Design. 2. On the Message tab, in the list, find and select the desired message. 3. Click Edit. 4. In the Mapping section, in the Target record pane, in the list, find and select the desired target record. 5. On the Mapping tab, on the Field mapping tab, in the list, find and select the desired field mapping. 6. Click the Field options tab. 7. Select the Dimension set check box. 8. In the Type field, select '0'. 9. In the Number field, enter a number. 10. In the Type field, select 'Dimension name'. 11. In the Name field, enter or select a value. 12. Close the page. Apply ledger Apply ledger To exchange journal data, you can get or set the account number for ledger transactions as main account (Default) or using another field (Ledger) to indicate if the value is, for example, a project, customer, or main account.Note: If the account type is Main account, only use the Ledger field option if one of these fields is part of the field mapping: LedgerDimension or OffsetLedgerDimension. Procedure 1. Click Connectivity studio Integration Design. 2. On the Message tab, in the list, find and select the desired message. 3. Click Edit. 4. In the Mapping section, in the Target record pane, in the list, find and select the desired target record. 5. On the Mapping tab, on the Field mapping tab, in the list, find and select the desired field mapping. 6. Click the Field options tab. 7. Select the Ledger check box. 8. In the Account type field, select an option. 9. Define which field of the target record table defines the main account. In the Account type field field, enter or select a value. Note: You can define any field of the document record table. Make sure, the defined field is set up for the relevant document record. 10. Close the page. Apply inventory dimension Apply inventory dimension On several D365 FO tables, inventory dimensions exist. Each inventory dimension is expressed in a RecId that refers to the Inventory dimensions (InventDim) table. So, it does not reflect the inventory dimension name and value. You can use the Inventory dimension option to get or set the inventory dimension value based on the RecId and the dimension name as defined for the field option. On import, you receive the dimension value. Based on the RecId in the target field and the selected inventory dimension, the value is set in the InventDim table. On export, based on the RecId in the source field and the selected inventory dimension, the dimension value is gotten from the inventory dimensions table. Note: On export, the source field type must be int64. Note:  Only use the Inventory dimension field option if the InventDimId field is the target field of the field mapping. For each used inventory dimension, add a separate field mapping. For example, if you use five inventory dimensions on a sales line, add five field mappings for the sales line target record. Each of these field mappings has the InventDimId field as target field. For each InventDimId field mapping, select the Inventory dimension field option and select the applicable inventory dimension. Procedure 1. Click Connectivity studio Integration Design. 2. On the Message tab, in the list, find and select the desired message. 3. Click Edit. 4. In the Mapping section, in the Target record pane, in the list, find and select the desired target record. 5. On the Mapping tab, on the Field mapping tab, in the list, find and select the desired field mapping. 6. Click the Field options tab. 7. Select the Inventory dimension check box. 8. In the Inventory dimension field, enter or select a value. 9. Close the page. Notes Instead of using the Inventory dimension field option, you can also apply inventory dimensions in another way. To do so: Add the InventDim table with the desired fields to your document. Add the InventDim document record to your message mapping and map the desired fields. Make sure that, in the mapping, the InventDim document record is added before the line to which you want to apply the inventory dimensions. In the line mapping to which you want to apply an inventory dimension, add the InventDimId field.   Apply external code Apply external code In a field mapping, you can apply an external code as defined for the related entity. As a result, on: Import, the external code is replaced with the related code in your D365 FO environment. Export, the code in your D365 FO environment is replaced with the related external code. You can only use the external code setup in messages that are run in EDI studio. To use the external code functionality, in EDI studio, additional external code setup is required for the EDI parties or EDI groups. For each EDI party or EDI group, you can define an external code definition as set up for a: Currency Released product Charge codes of miscellaneous charges Modes of delivery Terms of delivery Unit Procedure 1. Click Connectivity studio Integration Design. 2. On the Message tab, in the list, find and select the desired message. 3. Click Edit. 4. In the Mapping section, in the Target record pane, in the list, find and select the desired target record. 5. On the Mapping tab, on the Field mapping tab, in the list, find and select the desired field mapping. 6. Click the Field options tab. 7. Select the External code check box. 8. In the External code value table name field, enter or select a value. 9. In the External code value field name field, enter or select a value. 10. In the External code source record field, enter or select a value. 11. In the External code source field field, enter or select a value. 12. Close the page. Apply mapping variable Apply mapping variable During a message run, you can use mapping variables to temporary store values. You can write (calculated) values to a mapping variable, and later during the message run, read the value from the mapping variable. You can use mapping variables across records. The mapping variable values are only stored during the message run. When the message run is finished, the mapping variable values are deleted. During a message run, to read a mapping variable, on a field mapping, define the target field to be filled with the mapping variable value. Instead of a source field, use the 'Variable' field option to define the mapping variable which value must be used to set the target field value. Procedure 1. Click Connectivity studio Integration Design. 2. On the Message tab, in the list, find and select the desired message. 3. Click Edit. 4. In the Mapping section, in the Target record pane, in the list, find and select the desired target record. 5. On the Mapping tab, on the Field mapping tab, in the list, find and select the desired field mapping. 6. Click the Field options tab. 7. Select the Variable check box. Note: This check box is available only if a mapping variable is created for the message. If you have created a mapping variable, but the Variable field is not shown, refresh the page. 8. Click the Variables tab. 9. In the Source variable field, enter or select a value. 10. Close the page. End End

Activities

Name Responsible Description

Apply number sequence (Field option)

Application Consultant

You can use a number sequence to get the field value. So, instead of the source field value, the next available number in the number sequence is the applicable value.

Apply display method (Field option)

Application Consultant

You can use a display method to get the applicable value. For example, you can use a display method to calculate a value.

Apply custom handler (Field option)

Application Consultant

You can use a handler class to set the target field value. Several handler classes are available. For example, to get the current date, to add the time to a date, or to get the current company.

Apply custom expression (Field option)

Application Consultant

You can use an expression to modify the value. In the expression, use source fields, target fields, or mapping variables as variables.
As a variable in the expression, you can use a:

  • Field from any record of the applicable document. If you use a field from another record than the current record, make sure this record is mapped before the current record.
  • Mapping variable that is defined for the message.

Examples:

You can use an expression to:

  • Combine two fields. You can, for example, make a contact location name specific by combining it with the purpose. The expression can be: Description+'-'+Purpose. This results in, for example: Shop Main Street-Financial.
  • Calculate the unit price based on the quantity and line amount on a purchase order confirmation. The variables are from the source record: Qty (PurchLine, PurchQty field) and Amount (PurchLine, LineAmount field). The expression is: Amount/Qty.

Note: 

  • Usually, you use string and real values as variables.
  • Date calculations are not supported.
For more information on expressions, refer to: Expression.

Apply lookup (Field option)

Application Consultant

 		You can use a lookup to get a value from another table and use it as the output value of this option. For example, you can get a value from a table that is not in the source document.
The other table must have the source field as the single key field. The current value of the 'Modify a value' process is the input of the lookup. As a result, the value that is returned by the lookup is the value of the Return value field.
Before determining the output value of this option, you can apply a type conversion or a transformation.

Apply external reference (Field option)

Application Consultant

You can link an external ID to a record ID in D365 FO. Together with the external ID, you can also link an external revision number to a record ID.
The application, as defined for the connector, is used to store the link between the reference table and record ID in D365 FO and the external ID and revision number.
If you:

  • Export data, the applicable external ID or revision is searched for in the target connector application. If a record exists for the reference table and the source field (RecId) combination, the external ID or revision of this record is as the output value of this option.
  • Import data, the applicable target record ID is searched for in the source connector application. If a record exists for the combination of reference table and external ID and revision, the reference record ID of this record is the output value of this option. If no record exists for the combination, a record is created. The reference record ID of this record is the output value of this option.

Note: 

  • You can only link an external ID or revision number to a record ID if, on the applicable document, the External reference field and the Revision field are filled in for the source field or target field of the current field mapping.
  • You can only link a revision to a record ID in D365 FO if you also link the external ID. The external ID field mapping must precede the revision field mapping.
  • Usually, you use the External reference option on a field mapping where the source field (export) or target field (import) is the RecID.

Apply edit method (Field option)

Application Consultant

You can use an edit method to set the target field value. On import, the edit method changes the value in the target field of the D365 FO table.

Apply dimension set (Field option)

Application Consultant

On D365 FO tables, a financial dimension is expressed in a RecId to a financial dimensions table. So, it does not reflect the financial dimension name and value. You can use the Dimension set option to get or set the financial dimension value based on the RecId and the dimension name (or number) as defined for the field option. If the message is used to:

  • Import, you receive the dimension value. Based on the RecId in the target field and the name (or number), the value is set in the relevant financial dimensions table. Note: On import, the target field type must be other than String.
  • Export, based on the RecId in the source field and the name (or number), the dimension value is gotten from the relevant financial dimensions table. Note: On export, the source field type must be int64.

Note:

Only use the Dimension set field option if one of these fields is part of the field mapping:

  • DefaultDimension: This field is used to store default dimensions for, for example, customers, vendors, or customer groups.
  • LedgerDimension or OffsetLedgerDimension: These fields are used to store financial dimensions for ledger journals of the 'Main account' account type.
  • DefaultDimension or OffsetDefaultDimension: These fields are used to store financial dimensions for ledger journals of other account types.
This field must be the:
  • Target field of the field mapping for imports.
  • Source field of the field mapping for exports.
For each financial dimension that you want to set or get, use a separate field mapping. So, in the field mapping, you can have the same financial dimension field several times.

Apply ledger (Field option)

Application Consultant

To exchange journal data, you can get or set the account number for ledger transactions as main account (Default) or using another field (Ledger) to indicate if the value is, for example, a project, customer, or main account.

Note: If the account type is Main account, only use the Ledger field option if one of these fields is part of the field mapping: LedgerDimension or OffsetLedgerDimension.

Apply inventory dimension (Field option)

Application Consultant

On several D365 FO tables, inventory dimensions exist. Each inventory dimension is expressed in a RecId that refers to the Inventory dimensions (InventDim) table. So, it does not reflect the inventory dimension name and value. You can use the Inventory dimension option to get or set the inventory dimension value based on the RecId and the dimension name as defined for the field option.

  • On import, you receive the dimension value. Based on the RecId in the target field and the selected inventory dimension, the value is set in the InventDim table.
  • On export, based on the RecId in the source field and the selected inventory dimension, the dimension value is gotten from the inventory dimensions table. Note: On export, the source field type must be int64.

Note: 

  • Only use the Inventory dimension field option if the InventDimId field is the target field of the field mapping.
  • For each used inventory dimension, add a separate field mapping. For example, if you use five inventory dimensions on a sales line, add five field mappings for the sales line target record. Each of these field mappings has the InventDimId field as target field. For each InventDimId field mapping, select the Inventory dimension field option and select the applicable inventory dimension.

Apply external code

Application Consultant

In a field mapping, you can apply an external code as defined for the related entity.

As a result, on:

  • Import, the external code is replaced with the related code in your D365 FO environment.
  • Export, the code in your D365 FO environment is replaced with the related external code.

You can only use the external code setup in messages that are run in EDI studio.

To use the external code functionality, in EDI studio, additional external code setup is required for the EDI parties or EDI groups. For each EDI party or EDI group, you can define an external code definition as set up for a:

  • Currency
  • Released product
  • Charge codes of miscellaneous charges
  • Modes of delivery
  • Terms of delivery
  • Unit

Apply mapping variable

Application Consultant

During a message run, you can use mapping variables to temporary store values. You can write (calculated) values to a mapping variable, and later during the message run, read the value from the mapping variable. You can use mapping variables across records.
The mapping variable values are only stored during the message run. When the message run is finished, the mapping variable values are deleted.
During a message run, to read a mapping variable, on a field mapping, define the target field to be filled with the mapping variable value. Instead of a source field, use the 'Variable' field option to define the mapping variable which value must be used to set the target field value.

Activities

Name Responsible Description

Apply number sequence (Field option)

Application Consultant

You can use a number sequence to get the field value. So, instead of the source field value, the next available number in the number sequence is the applicable value.

Apply display method (Field option)

Application Consultant

You can use a display method to get the applicable value. For example, you can use a display method to calculate a value.

Apply custom handler (Field option)

Application Consultant

You can use a handler class to set the target field value. Several handler classes are available. For example, to get the current date, to add the time to a date, or to get the current company.

Apply custom expression (Field option)

Application Consultant

You can use an expression to modify the value. In the expression, use source fields, target fields, or mapping variables as variables.
As a variable in the expression, you can use a:

  • Field from any record of the applicable document. If you use a field from another record than the current record, make sure this record is mapped before the current record.
  • Mapping variable that is defined for the message.

Examples:

You can use an expression to:

  • Combine two fields. You can, for example, make a contact location name specific by combining it with the purpose. The expression can be: Description+'-'+Purpose. This results in, for example: Shop Main Street-Financial.
  • Calculate the unit price based on the quantity and line amount on a purchase order confirmation. The variables are from the source record: Qty (PurchLine, PurchQty field) and Amount (PurchLine, LineAmount field). The expression is: Amount/Qty.

Note: 

  • Usually, you use string and real values as variables.
  • Date calculations are not supported.
For more information on expressions, refer to: Expression.

Apply lookup (Field option)

Application Consultant

 		You can use a lookup to get a value from another table and use it as the output value of this option. For example, you can get a value from a table that is not in the source document.
The other table must have the source field as the single key field. The current value of the 'Modify a value' process is the input of the lookup. As a result, the value that is returned by the lookup is the value of the Return value field.
Before determining the output value of this option, you can apply a type conversion or a transformation.

Apply external reference (Field option)

Application Consultant

You can link an external ID to a record ID in D365 FO. Together with the external ID, you can also link an external revision number to a record ID.
The application, as defined for the connector, is used to store the link between the reference table and record ID in D365 FO and the external ID and revision number.
If you:

  • Export data, the applicable external ID or revision is searched for in the target connector application. If a record exists for the reference table and the source field (RecId) combination, the external ID or revision of this record is as the output value of this option.
  • Import data, the applicable target record ID is searched for in the source connector application. If a record exists for the combination of reference table and external ID and revision, the reference record ID of this record is the output value of this option. If no record exists for the combination, a record is created. The reference record ID of this record is the output value of this option.

Note: 

  • You can only link an external ID or revision number to a record ID if, on the applicable document, the External reference field and the Revision field are filled in for the source field or target field of the current field mapping.
  • You can only link a revision to a record ID in D365 FO if you also link the external ID. The external ID field mapping must precede the revision field mapping.
  • Usually, you use the External reference option on a field mapping where the source field (export) or target field (import) is the RecID.

Apply edit method (Field option)

Application Consultant

You can use an edit method to set the target field value. On import, the edit method changes the value in the target field of the D365 FO table.

Apply dimension set (Field option)

Application Consultant

On D365 FO tables, a financial dimension is expressed in a RecId to a financial dimensions table. So, it does not reflect the financial dimension name and value. You can use the Dimension set option to get or set the financial dimension value based on the RecId and the dimension name (or number) as defined for the field option. If the message is used to:

  • Import, you receive the dimension value. Based on the RecId in the target field and the name (or number), the value is set in the relevant financial dimensions table. Note: On import, the target field type must be other than String.
  • Export, based on the RecId in the source field and the name (or number), the dimension value is gotten from the relevant financial dimensions table. Note: On export, the source field type must be int64.

Note:

Only use the Dimension set field option if one of these fields is part of the field mapping:

  • DefaultDimension: This field is used to store default dimensions for, for example, customers, vendors, or customer groups.
  • LedgerDimension or OffsetLedgerDimension: These fields are used to store financial dimensions for ledger journals of the 'Main account' account type.
  • DefaultDimension or OffsetDefaultDimension: These fields are used to store financial dimensions for ledger journals of other account types.
This field must be the:
  • Target field of the field mapping for imports.
  • Source field of the field mapping for exports.
For each financial dimension that you want to set or get, use a separate field mapping. So, in the field mapping, you can have the same financial dimension field several times.

Apply ledger (Field option)

Application Consultant

To exchange journal data, you can get or set the account number for ledger transactions as main account (Default) or using another field (Ledger) to indicate if the value is, for example, a project, customer, or main account.

Note: If the account type is Main account, only use the Ledger field option if one of these fields is part of the field mapping: LedgerDimension or OffsetLedgerDimension.

Apply inventory dimension (Field option)

Application Consultant

On several D365 FO tables, inventory dimensions exist. Each inventory dimension is expressed in a RecId that refers to the Inventory dimensions (InventDim) table. So, it does not reflect the inventory dimension name and value. You can use the Inventory dimension option to get or set the inventory dimension value based on the RecId and the dimension name as defined for the field option.

  • On import, you receive the dimension value. Based on the RecId in the target field and the selected inventory dimension, the value is set in the InventDim table.
  • On export, based on the RecId in the source field and the selected inventory dimension, the dimension value is gotten from the inventory dimensions table. Note: On export, the source field type must be int64.

Note: 

  • Only use the Inventory dimension field option if the InventDimId field is the target field of the field mapping.
  • For each used inventory dimension, add a separate field mapping. For example, if you use five inventory dimensions on a sales line, add five field mappings for the sales line target record. Each of these field mappings has the InventDimId field as target field. For each InventDimId field mapping, select the Inventory dimension field option and select the applicable inventory dimension.

Apply external code

Application Consultant

In a field mapping, you can apply an external code as defined for the related entity.

As a result, on:

  • Import, the external code is replaced with the related code in your D365 FO environment.
  • Export, the code in your D365 FO environment is replaced with the related external code.

You can only use the external code setup in messages that are run in EDI studio.

To use the external code functionality, in EDI studio, additional external code setup is required for the EDI parties or EDI groups. For each EDI party or EDI group, you can define an external code definition as set up for a:

  • Currency
  • Released product
  • Charge codes of miscellaneous charges
  • Modes of delivery
  • Terms of delivery
  • Unit

Apply mapping variable

Application Consultant

During a message run, you can use mapping variables to temporary store values. You can write (calculated) values to a mapping variable, and later during the message run, read the value from the mapping variable. You can use mapping variables across records.
The mapping variable values are only stored during the message run. When the message run is finished, the mapping variable values are deleted.
During a message run, to read a mapping variable, on a field mapping, define the target field to be filled with the mapping variable value. Instead of a source field, use the 'Variable' field option to define the mapping variable which value must be used to set the target field value.
Related to Notes

Create mapping variables

 		 

See also

Provide feedback