Mapping Fields
- How do I access mapping fields?
- What are the options for the value class?
- What is Transfer-Fields functionality?
- What are the transfer rules of repositories to tables?
- What are the transfer rules of repositories to XML nodes?
- What are the transfer rules of repositories to JSON tokens?
Tip
Summary: Mapping Fields are used to set Field Values to a Record. Value Classes, such as Constant, Repository, Formula, and Partner can be used to determine the type of value for the field. Additionally, the Transfer-Fields functionality allows for automatic transfer of fields from one record to another. Depending on the type of repository, different rules are used for the transfer.
Mapping Fields are used to set Field Values to a Record. It is important that the Value corresponds to the Field Type. Additional actions can be used, like validation of values for Tables.
Field values are usually stored in the record only after a Mapping Line has been executed. In most cases, access to a field value in the same Mapping Line after it has been modified will return the old value.
The Media and MediaSet field types can be exported or imported by COSMO Data Integration Framework. For an export, the first entry inside the media set is used. Importing in a media set will always create a new media entry. Export and import of field type Media will replace the existing field value.
Mapping fields vary depending on the Repository Type. In a Table repository or Record Pool repository, a field represents an integer that indicates the actual field name of the table. In an XML Node repository, JSON Token repository, or SharePoint List repository, a field corresponds to a text value that reflects the technical name of the field. The Repository Type is specified in the Repository Code field of the Mapping Line or in the Repository Code for a Value Class configuration of the type Repository. Accessing a field value of any repository thus requires the correct configuration of Value Class, Repository Code, and Field.
To open the mapping fields
- Choose Fields in the Lines FastTab of the Mapping Version Card to access the Fields page.
- On the Fields page, fill in the fields as necessary. Hover over a field to read a short description.
Options for the value class
- Constant – A fixed value. The use of Mapping Variables is possible.
- Repository – A value of a Repository. The use of Mapping Variables is not possible.
- Formula – A calculated formula. The use of Mapping Variables is possible.
- Partner – A field value of a Partner. Only relevant if the Mapping is processed by a Partner Mapping.
For more information, see Value Classes and Field Values.
Transfer-Fields functionality
A special feature of the field transfer is the Transfer-Fields functionality. With this, all fields of Record A are transferred automatically to Record B. Therefore, Record B is defined within the Repository of the Mapping Line and Record A in the Transfer-Fields Repository Code field.
Transfer rules of repositories to tables
- From Table to Table: Field Values are transferred using the same Field Nos.
- From XML Node to Table: An associated XML Node is searched for each Field Name.
- From JSON Token to Table: An associated JSON Property is searched for each Field Name.
Transfer rules of repositories to XML nodes
- From XML Node to XML Node: All Node Values of the source are transferred to the target.
- From Table to XML Node: An associated XML Node is searched for each Field Name.
- From JSON Token to XML Node: An associated JSON Property is searched for each XML Node.
Transfer rules of repositories to JSON tokens
- From JSON Token to JSON Token: All JSON Properties of the source are transferred to the target.
- From Table to JSON Token: An associated JSON Property is searched for each Field Name.
- From XML Node to JSON Token: An associated XML Node is searched for each JSON Property.
Feedback
Submit feedback for this page .