Avoid syncing Content Types

Case 1: Destination content type has to be ignored

Assume you have a source endpoint with a content type: Destination and a destination endpoint with a content type: Destination. But each Content Type is manually input and manually maintained. You need to sync the content type to store a field value from the source content into a variable. Or you need to sync the content to populate the id-maps. But you don't want to sync the content type: Destination from the source endpoint to the destination endpoint.

Solution

ImpulseSync can solve this with noDeliver property in the job options.

Step 1: Create a job to sync the content type: Destination

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

Step 2: Set up the job options

• Next we set up the job options. Go to Add Job / Add Destination Endpoint section in the Job creation page and set the noDeliver property to true.