Once connected you should see a list of the fields from the source in the schema map, but the destination columns will read
<NONE> as we have yet to connect them together. In this example we have connected to the contacts entity in Dynamics CRM.
If you attempt to compare or synchronise while a destination field is still set to NONE, Data Sync will display an error.
It is always good practice to check you do not have a NONE field before comparing.
Fields can be mapped to the target in several ways:
Make sure you select a key column to act as a unique identifier. In this example we are using the email address as a way to uniquely identify a contact.
Once you have completed the mapping it will look something like this:
The source and destination can be compared by selecting 'Compare A -> B' on the toolbar.
This will load the data from the csv file and the contact entity and perform a reconciliation to identify any missing or changed items in the target. The reconciliation results will be displayed in the compare results panel.
Clicking on the green
+ will show a preview of the rows to be added.
Unchecking a set of results will mean that they will not be included in the synchronisation. In the example below the records to be deleted are not included:
To synchronise the changes between the csv file and Dynamics CRM contact entity, click on the 'Synchronise' button in the taskbar of the 'Compare Results' panel.
A dialog box will appear which allows you to choose whether to stop the processing in the event of any errors. Pressing start will begin the synchronisation.
When you have finished a synchronisation it is good practice to check that everything has been synchronised by Comparing A -> B again.
This should show that there are no records to update, such as in the example below.