You might need to have a process to delete relational table records in the event they are deleted in the source CRM object; otherwise, records are deleted in one place, and not deleted in the other, which amounts to synchronization inconsistencies between the CRM and the relational table.
The obvious requirement of any Scribe online synchronization to populate an Acoustic Campaign Relational Table is to insert and update the data. Deletions in CRM must be soft-deleted so that the record is available to query after the deletion.
For example, in Salesforce.com, a record is flagged as Deleted = true when the record is deleted. It is important because those deleted records continue to exist and can be queried out of Salesfore.com through the Scribe Online connector. If the source CRM record is hard-deleted, it disappears and is not available though the Salesforce.com APIs. In that case, the records cannot be queried out and consequently cannot be used to synchronize a delete to the relational table.
- Select the IS/MS - Include deleted items in query results setting within the Connection for Salesforce.com.
- Add an advanced map to your solution. The map must be the last map so that it runs last when the solution runs.
- On the Connection tab, select the Source object that uses the Salesforce.com connection.
- Add Filter.
- Choose Process all records on each run (or) Process only records created or updated since last run based on the value of the last modified field according to how you have setup the insert or update maps.
- On the Connection tab, select the Target object that uses the Acoustic Campaign connection.
- On the Fields tab, map the unique identifier from the Source object to the relational table unique ID.
- Click Ok.
Note
If your CRM object does not track deletes as described, you can work with your CRM administrator to build a process inside your CRM to put the object's Unique ID into a custom object during the CRM delete process. For example a Scribe mapping can reference the custom object that stores the deleted record IDs and synchronizes a Delete to the Acoustic Campaign relational table. In Salesforce.com, when a Source object is deleted, a trigger can copy the ID over to a Custom object. Alternatively, you can choose to delete all the rows in the Relational table (performed inside Acoustic Campaign) and then repopulate the Relational table through the Scribe sync with all current data.
Note
If your CRM object does not track deletes as described, you can work with your CRM administrator to build a process inside your CRM to put the object's Unique ID into a custom object during the CRM delete process. For example a Scribe mapping can reference the custom object that stores the deleted record IDs and synchronizes a Delete to the Acoustic Campaign relational table. In Salesforce.com, when a Source object is deleted, a trigger can copy the ID over to a Custom object. Alternatively, you can choose to delete all the rows in the Relational table (performed inside Acoustic Campaign) and then repopulate the Relational table through the Scribe sync with all current data.
Comments
0 comments
Please sign in to leave a comment.