Avoid overriding Fields

Case 1: Focal Point field under Image Wrapper content type has to be preserved

Assume you have a destination content type: Image Wrapper with a field Focal point that is a JSON field. See content model:

This field doesn't exist in the source endpoint. So the requirement in this case, is to be able to sync all the other fields without losing the Focal point value.

Solution

ImpulseSync can solve this with locked-fields property in the content mapper.

Step 1: Create a job to sync the content type: Image Wrapper

• First we create the job to sync the content type: Image Wrapper from the source endpoint to the destination endpoint.

Step 2: Set up the content mapper

• Next we set up the content mapper. Go to Field Locking section and set the Destination Locked Field property to focalPoint (the id of the field in the destination endpoint).

Step 3: Run the job

• Now we can run the job and see the results.