To maintain the relationship for creation of new records from external system into Database Source schema, the external application will have to establish relationship between the parent and child elements. To create a relationship in child or related table, the standard practice is to add a related column as REL[Source Table Name]ID to point to the primary key of "SYNC_ID" of the related / parent table.

Synchronization sequence example between Account and Contact:

• A new account is added with two new contacts in Database. The contacts table "SOURCECONTACT" will contain a column called "RELACCOUNTID".

• When the synchronization is initiated, the tool will do a check for "SOURCEID" on the Account record. In case the SOURCEID does not exist (which is Source id) it will initiate an insert operation into Source apps and update the "SOURCEID" back into that record in Database.

The system will do a check on SOURCECONTACT table and retrieve two new records without SOURCEID and updates those records with respective SOURCEIDs. At the same time it will find the external id, RELACCOUNTID and associates it to the right parent record into source applications.

Note:

Create a column with the following convention:

• RELXXXXXID where XXXXX is the name of the parent Table.** Example: RELACCOUNTID column on SOURCECONTACT showing that Contact has a relationship with Account.
• If the table is a custom field, then use RELXXXXX__C as the column showing relationship with another table.** Example: RELCONTACT_C column on SOURCESPECIALITYC showing that SPECIALITY_C has a relationship with CONTACT.