because you cannot lookup existing records in the destination or because data in the destination is altered by another process or by users, which makes a lookup useless.īy using an incremental block such as List new and updated contacts incrementally, you are - in theory - certain that each record from the source is only processed once. This could be needed if an Upsert is impossible to do, e.g. Sometimes you need to make sure that data from the source is processed only once and never sent to the destination more than once, in order to avoid creating duplicates in the destination. This risk can be eliminated by writing an external id from A in objects in B (see paragraph matching objects). For example, you should not delete data in B that is missing in A, when the data in B does not originate from A. This is a risk, if a mistake is made in the Compare Blend, you may end up deleting data in B mistakenly. Some platforms have a Webhook available on delete.Īnother solution is to build a Compare automation and delete in B what is missing in A. It's hard to detect which data was deleted in A because most API's do not expose this information. When an object is deleted in A, it may also need to be deleted in B. triggered from a Webhook), make sure to add logic to look up the parent object and add the link (foreign key), and add logic to create the parent object if it does not exist yet. When child objects are created or updated in a separate automation (which is e.g. Make sure to create parent objects first before creating child objects (e.g. when using a combined key name + date + location for an Order). Also be careful with spaces (make sure to trim keys) and with keys that may be truncated in the destination because of limited key length (e.g.
A good example is phone numbers, that may be formatted differently in A and B.
also in a Compare object block when checking if an update is needed. If transformations are needed on keys, make sure to perform these transformations rigorously everywhere, e.g. An example is Contacts where email addresses are unique in A but not in B. If the key is not unique in one of the platforms, store the id of A in the object in B as an external id and use this for matching. email address for Contacts, or name + date for Projects. Matching objectsĬhoose a unique key to match objects between A and B, e.g. Make sure that fields which are not included in your update do not cause these fields to be emptied in the object that is updated. Missing fields in update cause field to be emptied
0 kommentar(er)
