Configuring DemandTools deduplication process to select the Community User record as the ‘winner’?

Step 1: Create a checkbox field on the Contact object

Create a checkbox on the Contact object to be used to ‘flag’ Community Users:

1. Navigate to Setup and search for Customize.
2. Click on Contacts and then Fields.
3. In the “Contact Custom Fields & Relationships” section, select New.
4. Select Data Type = Checkbox, select Next.
5. For Field Label, enter TargetX Community User [or a Value of your choosing].
6. For Default, select Unchecked.
7. Click Next.
8. Select to make the field visible for only the System Administrator profile.
9. Click Next.
10. Select to include the field on the Contact Layout.
11. Click Save.

Step 2: Set Permissions to new field for Community Users

1. Navigate to Setup and search for Profiles.
2. Click on the Profile Name for your Community User profile.
3. Click on Object Settings.
4. Click on the Contacts object.
5. Selec Edit.
6. Navigate to the ‘Field Permissions’ section.
7. For the field you created, select Read Access and Edit Access.
8. Save your changes.

Step 3: Add new field to Application Form

In this step, you will add the new field to an Application Form as hidden and set a default value.
 

1. Select the Application Form tab and select the Application Form where you want to add fields.
2. Select the form you want to have new users ‘flagged’.
3. Select Form Builder.
4. Expand the Application/Contact section of the form.
5. Search for your new field and drag it onto the form.
6. Select the Properties icon (gear).
7. Check the Hidden checkbox.
8. Set Default Value to checked.

9. Select Ok.
10. Save and Publish the form.
11. Repeat for any additional forms you wish to have the flag set.

When an applicant saves a new application, the checkbox on the Contact object will be checked. You can now use this checked flag as criteria in your DemandTools deduplication process.

Step 4: In DemandTools, use the field you created as criteria to indicate the winner of the merge

If you are using the Salesforce merge functionality, please see Considerations for Merging Contacts Associated with Portal Users.