Map Xml Data Processor
The Map Xml data processor allows you to map harvested data to values defined in an xml file using
XPath expressions. The processor may execute a sequence of expressions in order to select the desired value.
The Map Xml data processor it typically applied to manual leaves, i.e. leaves that do not get their values during harvesting.
| Data processor |
| Name |
The name of the data processor currently in use by the selected leaf. To change data processor, select the name property and click on the ellipsis button. Select the appropriate data processor in the form that is displayed. |
| Settings |
| Expressions |
A list of XPath expressions to execute. Select the property and click on the ellipsis button to display the expression editor. |
| Xml file path |
The path to the Xml file containing your map data. |
Expressions
The XPath and Fallback columns are format strings, please see
MSDN for more information on format strings, allowing you to use harvested data in your expressions. Add the source columns you need in your expressions. When using the specified source columns in your format strings, the first column has index 0, the second 1 and so on.
Independent of the namespace prefix actually used in your Xml file, use the namespace prefix p in your XPath expressions. E.g. to select some element where the value of some attribute = value of the first source column:
//p:someelement[@someattribute="{0}"]
If you harvest a column that contains the short for the week days, but you want to store the full name of the week days, you can create an xml file as the one displayed below, and use the xpath expression described above, i.e. //p:someelement[@someattribute="{0}"].
Enter the XPath expressions you need. The first expression is executed relative to the root of the Xml document and thereafter every expression is executed relative to the matched node of the previous expression. The result of the dataparser is the inner text of the matched node of the last expression.
Every expression has a fallback option defining what should happen if the XPath expression fails to get a match. The default option is to abort the execution if there is no match, but you can also set the value to null or to the result of a format string. If a fallback is executed, the execution ends there, i.e. any succeding expressions will not be executed.
If an XPath expression results in more than one match, an exception will be thrown forcing the execution to abort.
Useful references
