Case 1: Content between endpoints already exist but have different ids
Assume there are 6 contents of type Bed in the source endpoint and 6 contents of type Bunk in the destination endpoint. You want to be able to sync those contents without creating duplicates. They have manually been created and have different ids. They have a code field that is unique across each endpoint and can be used to align the contents because they match across endpoints.
Solution
ImpulseSync can solve this by using the Content Aligner in the content mapper.
Step 1: Create a job to sync the content type: Bed -> Bunk
First we create the job to sync the content type: Bed from the source endpoint to Bunk into the destination endpoint.
Step 2: Set up the content mapper
Next we set up the content mapper. Go to Field Aligning section and set the Source Aligner Fields property to code (the id of the field in the source endpoint) and the Destination Aligner Fields property to code (the id of the field in the destination endpoint).
