Relationship
The relationship manipulator allows you to create a relationship field and relate to a destination content previously synced from the manipulated content.
This manipulator can only create a relationship using the same content. Meaning if the same source content is synced to the destination as multiple different content types, this manipulator can create a relationship field between those destination content types.
Properties
It is important to note that all these field... (i.e. fieldId, fieldType, etc) properties are motation properties, they have to use the same syntax as the motation system. Just like the ones used in the connector's Transformers.
| Property | Purpose | Required |
|---|---|---|
destinationContentType | The destination content type to search for a mapped ID with | True |
fieldId | ID of the field to add, must be unique | True |
fieldName | Name of the field to add | False |
fieldSystemType | Motation System type of the field to add | False |
fieldOrder | Order of the field to add | False |
destinationEndpointId | Destination Endpoint ID to use when manipulator used "on write" | False |
Specifics
How to use
The destinationContentType value is the value of the destination content type to search for an ID map with. Often this value is the destination content type set via a content mapper for a job this content was synced with previously.
Examples
Splitting a Source Content
In this example there is a source content type called People where each content has a two text values. One text value is the name. The other text value is the address. With this manipulator you can setup and run two jobs to split this into two contents at the destination and create a relationship between them.
Here you can see the example source content.
Two jobs are created to sync this same source content to the destination as two different contents. The first job syncs the address. The second job will sync the person and use the relationship manipulator to create an relationship field from the person to the address.
After the first job finishes, there is now this address content at the destination.
Before running the second job, we add a relationship manipulator. Below is the relationship manipulator config used.
After the second job finishes, there is now a person content at the destination which has a reference to the previously synced address content.
Last updated
