Custom Objects

Overview

Cloudingo supports deduping and importing against custom Salesforce objects, in addition to the standard objects like Leads, Contacts, Accounts, and Person Accounts. Custom objects are defined as any object that cannot be merged natively within Salesforce, including some standard objects like Opportunity, Case, and Campaign Member. Custom objects can also be true custom objects configured in the org.

Request Object

1. Custom merge is available with a Professional or Enterprise license.
2. Contact your Account Representative or email contact@cloudingo.com to enable the feature or a specific object.

Manage Object

1. Add fields for indexing in the Manage Objects section (optional).

Navigation

1. Choose 'Tools' → 'Dedupe' → 'Filters' from the left-hand-side navigation window to navigate to the merge filters dashboard where custom object filters can be created or managed.
2. Choose 'Tools' → 'Dedupe' → 'Rules' from the left-hand-side navigation window to navigate to the merge rules to edit an existing or create a new rule for the custom object.

Custom Object Filters

1. Filters are configured using the same logic as a standard object merge filter.
2. Create a new filter once the object is enabled.

Custom Object Rules

1. A 'Default' rule is automatically created when an object is enabled by Cloudingo.
2. Edit the existing rule or create a new one.
3. Custom object rules differ slightly from a standard object merge rule. Steps 1-3 of the rule are the same as a standard object merge rule. In Step 4, related object rule definitions are defined. See below.

Step 4: 

Default Rules

Cloudingo will default all related objects to ‘move’. This is the default and recommended setting.

1. Move: Reparents the related object data to the master record.
   1. Data is disassociated from the deleting/non-master record and moved to the master.
   2. Lookup Relationships will reparent automatically with this default setting.
   3. Master-Detail Relationships will reparent automatically with this default setting.
      1. In Salesforce, Master-Detail objects must have the ‘Child records can be reparented to other parent records after they are created’ setting enabled on the field that creates the relationship.
2. Do Nothing: Will not reparent any related object data during the merge.
   1. Data will be deleted with the non-master record or orphaned.

Specific Rules for Related Objects

Cloudingo will automatically detect which objects do not allow ‘move’ due to Salesforce restrictions and set up the necessary ‘Copy’ rules to prevent data loss.

To add a custom-related object rule:

1. Choose the ‘Add Related Objects’ option.
2. Choose the related object in the ‘Related Object’ drop box.
3. Related object field and relationship type will automatically populate from the Salesforce schema.
4. Choose the desired operation (move, shallow copy, or do nothing) in the ‘Operation’ drop box. If the default settings are already set to ‘move’, a specific rule is not needed to ‘move’. Specified rules are typically used to force a ‘shallow copy’ or to ‘do nothing’ (not query for the data).
   1. Move records into master record collection: Reparents the related object data to the master record.
      1. Data is disassociated from the deleting/non-master record and moved to the master.
      2. This option will only appear for objects that Salesforce allows the related data to be ‘moved’ vs. ‘copied’.
   2. Copy records into master record collection: Creates a new copy of the related object data and attaches it to the master.
      1. Data is retained on the deleting/non-master record and deleted with the object after merging. This allows for restoration if the deleted record is recovered from the Salesforce recycle bin.
   3. Do nothing: Will not query for related object data and will not reparent or copy any related object data during the merge.
      1. Data will be deleted with the non-master record or orphaned.