Splitting Content with Reference

Case

Assume that the source content is information for people. Such as name and address.

This content needs to sync to the destination, but as two separate content types. One content will have the person's address. The other content will have the person's name and a reference/relationship to the new address content.

We need to be able to:

1. Sync one content as two different content

2. Create a relationship between the two new destination content

Solution

ImpulseSync can solve this with two jobs and the relationship manipulator.

First create a job to sync the source people content as the destination address content.

This job doesn't have any special config or manipulators. It simply sets the content mapping to sync to the destination content address.

The second job to create is to sync source people content as the destination person content.

The content mapping for this job is set to the appropriate destination content type.

This job also has a relationship manipulator configured.

This config creates a new relationship field address_ref. This field will reference/relate to the destination address content the source people content was previously synced as.

Finally, the jobs can be run in order.

1. Run the job without the relationship manipulator to create the dependency content

2. Run the job with the relationship manipulator to sync the remaining content and create a relationship

Destination Address Content

Destination Person Content