Setup of XML mapping
When receiving electronic documents in Continia e-Documents Import the values in the electronic documents needs to be mapped to the fields in Microsoft Dynamics NAV or Microsoft Dynamics 365 Business Central on premises. The mapping is placed in the XML version table.
You must import the XML mapping to be able to receive and process e-documents.
To import the XML mapping that contains the information needed to successfully import the supported UBL-formats follow the steps below.
- Choose the icon, enter Import XML Version.., and then choose the related link.
- On the XML Version Import/Export request page, choose the OK button.
- On the Import dialog, browse to the XML-Layout.txt file. A progress window now appears.
When the progress window disappears the XML mapping is imported.
You can find the XML-Layout.txt file in the product folder. The file is located in the subfolder XML-Layout under the Support Files folder.
The table contains a definition of each element in the supported UBL-formats. The table is built in a structure like an XML document. Each element in the XML document represents a record in the table. The table then holds information about how to process the individual elements. The table is populated when importing the XML-Layout.txt file.
- Choose the icon, enter XML Version, and then choose the related link.
Below you will find a detailed description of each field.
|Expand||Displays if all the child elements of a record are shown in the page. If the field has value 0 it means that child elements are not shown. Any other value means it shows all child elements. The field is not editable and is only for information. |
The value of the field is changed when choosing the Expand All, Collapse All or Expand/Collapse actions on the XML version page.
|XML-Version||Here you can enter a code to identify the UBL-format and document type. The entered code must be unique.|
|Tag Type||Here you can choose the type of XML tag. The following options are available:|
The empty value must be used if the element is not a header tag.
The HeaderTag option must be used to identify an XML tag that contains other tags.
The EndHeaderTag option must be used identity the end XML tag of a header tag.
|Data Type||Here you can choose the data type the data must be converted to when importing the data. The following options are available:|
The datatype you choose must match the datatype of the Field – Import field if the Data in processing field is set to Field.
|Level||Here you can enter a number to set the level of the element. The setting specifies where in the structure of the file the element is placed. The number specifies how many parent elements it has. If the value is 0 it means root level.|
|Tag Name||Here you can enter the name of the tag in the XML file. The value is automatically uppercased.|
|UDT||You can select this checkbox if the record is user defined (User Defined Tag). If you change any of the standard mappings imported from the product folder the field will be enabled.|
|Data in processing||Here you can choose how the processing of data is done. The following options are available:|
If you choose the option No the element is not to be processed when importing documents.
The option Constant is currently not in use.
If you choose the option Field the element is mapped directly to a field without any data processing.
If you choose the option Special the element is processed by code in Continia e-Documents Import and then mapped to a field either defined in the code or in the specified in the Table – Import and Field - Import fields.
If you are mapping custom fields or fields not part of the standard mapping you may need to add customized code.
|Mandatory||The field is currently not in use.|
|Mandatory Not Blank||The field is currently not in use.|
|Interactive Tag||The field is currently not in use.|
|Only Invoice||The field is currently not in use.|
|Blank Zero||The field is currently not in use.|
|Field Length||Here you can enter the maximum length of the data. The length must match the length of the field the data is mapped to (Field - Import).|
|Decimal Rounding 1||The field is currently not in use.|
|Decimal Rounding 2||The field is currently not in use.|
|Special Handling Code Import||Here you can enter a predefined instruction to process the element in a special way. The following predefined instructions can be handled by Continia e-Documents Import:|
If you enter COMMENT in the field the data in received document will be inserted as comments in the Received Comments table. The comments can be accessed on the Document Journal page or the Received e-Document page.
If you enter ADVICE in the field the data in received document will be inserted as comments in the Received Advice table. The advice can be accessed on the Document Journal page or the Received e-Document page.
If you enter one of the predefined instructions the Data in processing field must be set to Special.
|Condition||The field is currently not in use.|
|Dependent||The field is currently not in use.|
|Repetitive Group||The field is currently not in use.|
|Table – Import||Here you can choose the table you want to import data into. If you select a value in this field, you must choose a value in the Field – Import field.|
|Field – Import||Here you can choose a field from the table specified in the Table – Import field you want to import data into.|
|Table Import Name||Displays the name of the table entered in the Table – Import field. The field is not editable and is only for information.|
|Traverse Table||The field is currently not in use.|
|Traverse Table Name||The field is currently not in use.|
|Parent||Displays the line no. of the nearest parent element of the record. The field is automatically populated by using the Check level and create parents action on the XML version page.|
|Parent Tag||Displays the nearest parent element of the record. The field is not editable and is only for information. The field is automatically populated by using the Check level and create parents action on the XML version page.|
|Parent Tag Chain||Displays the parent elements all the way to the root element of the record. The field is not editable and is only for information. The field is automatically populated by using the Check level and create parents action on the XML version page.|
|Line No.||Displays the line No. in the XML version. The field is automatically populated by inserting a new record. The field is not editable and is only for information.|
We recommend that you do not create the XML version manually. When changing the XML version it could end up being invalid and thereby blocking import of feature documents.