Step 2b: Content mapper

Overview of content mapper key concepts

The content mapper is the key feature to make any sync work from any source platform to any destination platform, but how does the content mapper work? We take the content coming in from the source put it into impulsesync's content lake house and transform the data into something that we can map from the source to the destination. Now to talk about config we have a variety of ways and options to configure and it can be a bit overwhelming, but lets break it down step by step. Step 1: Selecting endpoint and content type When your editing your content mapper select the endpoint that is attached to that job, you wont be able to select any endpoints outside of those that are labled as destination endpoints in the job, if you have multiple endpoints set at a destination you can simply click the one that you want to set up first. (NOTE: it is recommended to have configuration for all endpoints being used as a destination) After setting up the endpoint the next thing to do is setting up the content type, now we have connectors that will pull the data from the platform and give you a drop down to select your content type in the destination platform your trying to sync into. If you dont have this feature with the connector that your endpoint is hooked up to, then its very simple fill the content type field with whatever variable your platform identifies their content type with the same content type variable that you filled in with the job settings once set your good to go!

Step 2: Field mapping Field mapping sounds a little complicated but its actually not that intense, the way to break it down is similar fields for instance in dotcms we have a WYSIWYG field the closest similar field that can handle large amounts of texts with markup options is the rich text field in strapi so we will be mapping the WYSIWYG field from the source to the rich text field in the destination. Lets break this down a little more we just need to add 1. source field variable name 2. destination field variable name and 3. and a field type this is what impulse uses to verify what exactly needs to be mapped and how it needs to be mapped.

Now guessing can be a little tough sometimes and often a little bit much to think about when we are moving large content type structures from source to destination, we have a two solutions to this dilemma. We have similar features to selecting endpoints in the mapper on some supported connectors it will show a list of the content inside the content type and show which fields need to be mapped and auto set up the configuration aswell. Additionally if the connector does not support pulling the fields of the content type we can find out what fieldtype we need through our connector matrix.

The rest of these options for the content mapper are optional but they are additional features to the content mapper that we will quickly go over. -Locking field: This is a additional mapping option that will lock whatever field variable is provided with . Meaning whatever field you add in the locking field mapper that field will NOT change when syncing content over from the source to destination. -Field Aligner: This allows us to match content and update content that was already living in the destination if we have content we just want to update we can match ids from the source to the destination and update these fields.

Step 3: Save Changes Now with our content mapping set up we just need to save changes its all pretty easy from here click the save mapper button and anytime you need to edit it or change the mapping you just hit edit from the jobs page and select the endpoint that you have the mapping saved to. The mapping gets saved to each individual endpoint attached to a job.

And once again if your following along it should look something like this