Appendix: XML mapping GUI - Revision history

Onea: /* Define new XML Mapping in the application */

2016-11-09T10:49:30Z

‎Define new XML Mapping in the application

Show changes

Onea at 10:56, 4 November 2016

2016-11-04T10:56:58Z

Show changes

Onea: Onea moved page Appendix: XmlMappingGui to Appendix: XML mapping GUI: wrong name

2016-11-04T08:36:14Z

Onea moved page Appendix: XmlMappingGui to Appendix: XML mapping GUI: wrong name

Onea: /* Identifying mapping types */

2016-10-26T09:44:48Z

‎Identifying mapping types

Onea: /* Identifying mapping types */

2016-10-26T09:44:04Z

‎Identifying mapping types

Onea: /* Identify XML */

2016-10-26T09:43:13Z

‎Identify XML

Onea: /* Identify mappings */

2016-10-26T09:37:53Z

‎Identify mappings

Onea: /* Identify mappings */

2016-10-26T09:37:14Z

‎Identify mappings

Onea at 09:36, 26 October 2016

2016-10-26T09:36:54Z

Onea: /* Identify mappings */

2016-10-26T09:32:25Z

‎Identify mappings

@@ Line 50: / Line 50: @@
 [[File:EditMappingType2.png]]
-The application allows to remove certain unused nodes, or to mark some nodes as identifying columns by clicking on the nodes.
+The application allows to remove certain unusable (for mapping) nodes , or to mark some nodes as identifying columns by clicking on the nodes.
 By clicking the [[File:addIcon.png]] icon, the xml (or another xml with same rootnode and namespace ) can be re-uploaded to add additional nodes.

@@ Line 44: / Line 44: @@
 [[File:EditMappingType1.png]]
-The Root element and its namespace is read from the example Xml File and can’t be changed.
+The Root element and its namespace is read from the example xml file and can’t be changed.
 The tree structure of the xml file is shown.

@@ Line 19: / Line 19: @@
 : 1. <code><?xml version="1.0" encoding="UTF-8"?><Invoice> <amount></amount> ….</Invoice></code>
 :: Will be identified as an Xml with the root Element Invoice and an empty namespace, and no other identifying elements
 :: {{info|This setup is strongly discouraged.}}
 : 2. <code><?xml version="1.0" encoding="UTF-8"?><Invoice><implementation>customer 1</implementation><amount></amount>……. </Invoice></code>
 :: Will be identified as an Xml with the root Element Invoice and an empty namespace, but this time we will define that the element “implementation” is an additional identifier for the Xml with this root element.

@@ Line 70: / Line 70: @@
 The mapping name, document type and values for the identifying columns are mandatory to be able to save a mapping.
 When selecting the document node (this is the node in the xml tree that represents an invoice), 2 additional tabs ‘Header Mappings’ and ‘Other Mappings’ are shown.
 When selecting the postingline node (this is the node in the xml representing the invoice lines), an additional tab ‘Posting Line Mappings’
 The partner field allows to map the supplier or customer based on field in the xml. If this field is filled out another additional tab ‘Partner Mappings’ is shown.

@@ Line 54: / Line 54: @@
 ==Identify mappings==
 [[File:addMapping.png]]
 Once mapping types are defined we can go along and define the actual mappings.

← Older revision	Revision as of 08:36, 4 November 2016
(No difference)

@@ Line 77: / Line 77: @@
 When selecting the “Header Mappings” tab a list of all header fields will be shown.
-For each header field a node can be selected by clicking the   icon. If a node is selected the value of the header field will be filled out with the value of the node in the xml field.
 Note : not all header fields have to be mapped to a node.
 Eventually a formatter can be added. This formatter will format the data in the Xml file in a specific way to fill out the header field. (example date formatter)

← Older revision		Revision as of 09:32, 26 October 2016
Line 65:		Line 65:

	If a mapping is defined specifically for a company (company of the mapping is not null) this mapping is preferred to the general mapping for all companies (company of the mapping is null).		If a mapping is defined specifically for a company (company of the mapping is not null) this mapping is preferred to the general mapping for all companies (company of the mapping is null).
		+
		+	[[File:editMapping1.png]]
		+
		+	The mapping name, document type and values for the identifying columns are mandatory to be able to save a mapping.
		+	When selecting the document node (this is the node in the xml tree that represents an invoice), 2 additional tabs ‘Header Mappings’ and ‘Other Mappings’ are shown.
		+	When selecting the postingline node (this is the node in the xml representing the invoice lines), an additional tab ‘Posting Line Mappings’
		+	The partner field allows to map the supplier or customer based on field in the xml. If this field is filled out another additional tab ‘Partner Mappings’ is shown.
		+
		+	===Header Mappings ===
		+	[[File:editHeaderMapping.png]]
		+
		+	When selecting the “Header Mappings” tab a list of all header fields will be shown.
		+	For each header field a node can be selected by clicking the icon. If a node is selected the value of the header field will be filled out with the value of the node in the xml field.
		+	Note : not all header fields have to be mapped to a node.
		+	Eventually a formatter can be added. This formatter will format the data in the Xml file in a specific way to fill out the header field. (example date formatter)