Shared Key: A shared key can be set to indicate how your systems should match the data between your applications.
I am getting an error “Has not set sharedKey DSYNCid” what does this mean? Usually this is because you have not set your shared key on a one direction data transfer. To specify what your shared key is click on the destination endpoint then on the right-hand side your shared key section will appear on the right hand panel. This key will be the primary key that DSYNC will use to pair or correlate your sync. This shared key will be the link between the same record in both systems. Within the shared key section you can specify in the drop down what field you would like as the shared ID.
Shared key NOTEs:
You must make sure that if you select a field to be a shared field that it is mapped in your mapping section. The shared key is your primary key that DSYNC can use to make the updates. Shared keys have to be mapped to something unique in the systems. A good example of shared keys are ORDER ids or SKUs or for customers it could be email address to identify a unique field on the system to update. Inventory could be SKU, customer could be email.
Shared key When you create a link between two real time jobs you can still set up the direction of the flow. One way is more for one way APIs syncs.