Mapping CSV Rows to Documents
CSV rows and documents are mapped by defining a CSV key field and a CORE key field.
You can choose different types of fields for mapping CSV rows to CORE documents.
- The
ID (
rm_numeric_identifier) field . - A single value, multivalue or hierarchical field. The system will map CSV rows to documents with the same field value.
- A text field. To identify documents that can be mapped to CSV rows, the system will use field based search, with any expression allowed for a single field’s content.
If a CSV row does not match any document, it will be ignored.
In the
mergeCSV.bat, the
-idCSV defines the CSV key field. Thee
-idEngine parameter defines the CORE key field.
In the CSV Merge Wizard, map the key fields in the Field Defnition step and select Key in the Type column.
Attention: If more than one line matches the same document, only the first one will be considered, later changes will be ignored for an already changed document. This does also apply if family expansion is enabled. For example, if an attachment matches a CSV row due to family expansion, and later the same document matches a CSV row because the CSV and the CORE key fields match, then this second one is ignored.
Multiple document matches
If the CSV key matches multiple documents, all or no documents are mapped.
To allow multiple documents matching, in the
mergeCSV.bat script, use the
-allowUpdateMultipleDocs parameter.
In the CSV Merge Wizard, the Allow changing of multiple documents option must be activated in the Additional Options step.
Non-exact document matches
By default, the CSV and CORE key fields must exactly match each other. You can allow that the document’s CORE key field must not exactly match, but only contain the CSV key string.
To allow non-exact matches in the
mergeCSV.bat script, use the
-noUniqueMatch parameter.
In the CSV Merge Wizard, activate Allow non-exact document matching in the Additional Options step.
Note: For single value, multivalue and hierarchical key fields, only exact document matches can be used.
Mapping options summary
| Field type used | Field content match | Multiple document matches |
|---|---|---|
ID (rm_numeric_identifier)
|
exact match or non-exact match | allowed or not allowed |
System ID (uri containing
the data source name and the URI)
|
exact match or non-exact match | allowed or not allowed |
| Single value, multivalue or hiearchical field | field value restriction | allowed or not allowed |
| Any other field | exact match or non-exact match | allowed or not allowed |