In addition to the standard objects already supported (leads, contacts, accounts, and person accounts if enabled), Cloudingo can also be configured to allow for deduping and/or importing against your custom Salesforce objects (such as opportunities, cases, or other specific custom objects you have configured within your Salesforce org). To dedupe against one or more of your custom objects, contact your account representative (or email firstname.lastname@example.org) to get this feature enabled.
Once Custom Objects has been enabled for your org by your Account Representative, you will be able to see the custom object enabled in your Cloudingo account.
- Click on the ‘Admin’ menu in the top, right corner.
- Click on ‘Objects’.
Once in the Manage Objects page, you should see your custom object in the list (see image below). Click the arrow to the left of the object to view the indexed fields. Indexed fields chosen here are fields that Cloudingo will always keep indexed. These will be fields on the object that will be used when creating filters to identify your duplicates. Indexing the fields in this section prevents a re-index from triggering on the object when creating new filters. If you fail to include a field in your indexed fields that you need in one of your filters later, that is alright. You can always add them to the filter and the field will be indexed at that time. Fields that appear in black boxes without an ‘x’ to the right hand side are required fields on the object and cannot be removed.
*To add additional fields to your indexed list, click the ‘Edit Fields’ button at the bottom right corner. This will pull up a list of all available fields on the object.
Cloudingo will automatically create one generic dedupe filter on your custom object. The filter configuration works exactly the same as it does on Standard objects. You can create new filters (from the action menu on the dedupe dashboard) or edit the generic filter (click the filter menu option and choose Edit) to specify the matching criteria for your custom object.
Cloudingo also automatically creates one generic automation rule for your custom object. The automation rule configuration is slightly different than the Standard object rules. You can create new automation rules or edit the generic default automation rule for your object by going to the Automation menu from your dedupe dashboard, then clicking Manage Rules. By default, the default automation rule for your custom object is already tied to the generic filter that is created (and any future filters you create).
The only difference between the automation rule for custom objects and the automation rule for standard objects is there is an additional 3rd tab in the rule configuration for custom objects. For more information on the basic automation rule configuration for Tab 1 and Tab 2, please click here.
In Tab 3 of the custom rule configuration, you will have the ability to setup additional rules related to Relationship Objects.
Cloudingo has developed our own proprietary merge process to accommodate custom objects. In the merge process on custom objects, you can either choose to ‘move’ the related object data from the non-master/deleted record over to the master/surviving record. When you ‘move’ data, it will take the related object data from the non-master record, and re-associates that data to the master record (disassociating the related object data from the non-master record immediately prior to the deletion of that record).
You also have the ability to ‘copy’ the related object data from the non-master/deleted record over to the master/surviving record. When you ‘copy’ data, it will take a COPY of the data from the non-master record, and create a new related object to mimic the old record’s data and attaches it to the master/surviving record. The old related object will remain on the non-master record and gets deleted with the object during the merge process. If you ever have to restore the object from Salesforce recycle bin for any reason, the related object data would still be in-tact.
- By default, Cloudingo will move (re-parent) all lookup relationship object records to the master record if they are not already associated. You can configure the rule to ‘Do nothing’, which will not move or copy the lookup relationship object records to the master. By choosing ‘Do nothing’, the lookup relationship object records will be orphaned (or deleted) with the non-master record.
- By default, Cloudingo will move (re-parent) all master-detail relationship object records to the master record. You can configure the rule to ‘Do nothing’, which will not move or copy the master-detail relationship object records to the master. By choosing ‘Do nothing’, the master-detail relationship object records will be orphaned (or deleted) with the non-master record.
- You can configure specific related object rules to handle each related object individually. Specific related object rules will take precedence over the default rule behavior.
To add a custom related object rule:
- Click ‘Add Related Objects’ from the bottom, right corner.
- Choose the Related Object from the drop box in the related object column.
- The related object field & relationship types will pull in automatically. Review these for accuracy.
- Click the Operation drop box to choose how you want to handle the related object (move, copy, or do nothing).
- The ‘Move records into master record collection’ option re-parents the related object data to the master; removing the original related object from the non-master object.
- The ‘Copy records into master record collection’ option creates a new copy of the related object and attaches it to the master; leaving the original related object attached to the non-master object (which is then deleted with the object after merging). The copy function allows for restoration if the object is recovered from the Salesforce recycle bin after deletion.
- The ‘Do nothing’ option will not copy or move the related object records to the master; the related object records will be orphaned (or deleted) with the non-master record
Salesforce does not always allow a ‘move’ on a related object. In these instances, as long as you have not configured ‘Do Nothing’ as your default rule or specific related object rule, and you configured ‘move’ as your default rule, we will always (by default) perform a ‘copy’ to the master related object (even if a specific related rule is not configured). Lookup related objects only allow ‘copy’. ‘Move’ is not allowed.