FAQs

1)After importing the solution of DeDupeD from website all the Processes of DeDupeD is in a 'Draft/Deactivated' state. What to do?

Once the solution is imported, please follow the below steps to activate all the processes of DeDupeD.

• Click on the gear icon --> Select Advanced Settings.

• Next, select Processes.

• From 'All Process' View activate the process shown in the below screenshot:

2) Which entity view should be modified to show up columns from a specific entity view when merging the duplicate records?

To view the columns of an entity view on the DeDupeD UI and Windows tool while merging the duplicate records. Select your desired view in the “Entity View” field within “Duplicate Matching Rule Settings”.

For instance, if you select the “All Contacts” view in the entity view field, then you will be able to see the columns of the “All Contacts” view on the DeDupeD app and tool, interface while merging duplicates.

DeDupeD UI: In the below screenshot, you can see how entity view columns appear on DeDupeD app UI.

DeDupeD Tool: In the below screenshot, you can see how entity view columns appear on DeDupeD Tool.

3) I want to check all the duplicates of my entity view records at once. How can I see them?

With DeDupeD’s windows tool, you can easily see all the duplicate records of an entity view at once.

To see all the duplicates of an entity view, follow the steps below:

• Once logged into the tool, select any one of the configured entities.

• Select the specific entity view for which you want to see the duplicates.

• Click on “Find Duplicates” button.

• Now you can see all the duplicate records of your selected entity view at once.

4) Can we restrict creating duplicate records while importing them from an Excel sheet?

Yes, with DeDupeD, you can restrict creation of duplicate records while importing data from an Excel sheet.

For this, you will need to enable the Server-Side DeDupeD Settings. Here, you need to select both ‘new record’ and ‘existing record’ plugins to prevent duplicates on events such as creation of new records and updating existing records.

• If OOB Duplicate Detection is not disabled you will need to set Allow Duplicates toggle to ‘No’ while importing the Excel Sheet.

5) How to identify the number of users in my CRM that will be considered for licensing?

Step 1: Log in to CRM and open the Sales Hub App

Step 2: Click on the Advance Find Option present in the right top corner (shown below)

Step 3: In the search bar, search for “User” keyword. Select the User entity and click on the Continue button

Step 4: Once clicked, a side panel will show up containing default conditions. Clear the condition by selecting “Delete all Filters” and apply the below conditions in the filter section as shown below

a. Status Equal Enabled

b. Access mode Equal Read-Write

c. Restricted Access Mode Equal No

d. Primary Email address Does not Equal [email protected]

Step 5: Add a new related entity condition, where you will find the Security Role option under the Many to many sections as shown below

Step 6: By default, contains data Operator will be selected which will retrieve only those users who have a security role assigned.

Delete the related entity field condition as shown in the screenshot below and then click on the Apply button to provide you with the list of respective users.

6) We have done a sandbox copy of the production environment to a TEST environment and would like to work with the 'DeDupeD' solution in this new instance. What should we do?

For this, you need to delete the Inogic License Details record from your sandbox environment. After deleting, the next step would be to activate the license.

To delete the DeDupeD license follow the steps given below:

• Click on the Gear icon and go to Advanced Settings.

• Navigate to Advanced Find.

• Select Inogic License Details in ‘Look for’ -> Click on Results button.

• Select the DeDupeD record and delete it.

7) Unable to Configure the Application Due to Block Unmanaged Customizations in Dataverse?

When installing our solution, it's crucial to address certain prerequisites beforehand to ensure a smooth deployment process. One of these prerequisites involves disabling the "Block Unmanaged Customizations" feature within the Power Platform administrator settings.

Because while configuring our solution, certain required unmanaged customization takes place, for which this setting needs to be turned OFF.

Below are the steps for the same:

1. To disable this feature, navigate to Power Platform Admin Center and Log in to the Power Platform Admin Center using your administrator credentials.

1. Navigate to Environments: Select the environment for which you want to disable the setting from the list of available environments.

1. Access Environment Settings: Within the selected environment, navigate to the "Settings" tab to access environment-specific configurations.

1. Access to Customization Settings: Navigate to “Product” dropdown & Click on “Features”.

1. Disable "Block Unmanaged Customizations": Locate the "Customization Settings" section and toggle the "Block Unmanaged Customizations" option to the "Disabled" position.

1. Save Changes: Once you've disabled the setting, don't forget to save your changes to apply the configuration to the environment.

8) How does the product ensure data security, and does it transfer any data outside the environment where it's stored?

No, we do not store any data on our end. All data is sourced directly from Microsoft through the Out-of-the-Box (OOB) APIs. Our product operates based solely on this data to perform its logic and functions. Consequently, all data processing occurs within the original environment, ensuring that no data is transferred offshore or outside of that environment.

9) How can I set a customized status reason for merged records in DeDupeD?

In DeDupeD, when duplicate records are merged, subordinate records are automatically set to Inactive. If your organization uses custom status reasons—like Lost, Canceled, or Disqualified—this default behavior can cause errors or mismatched statuses. To prevent this, DeDupeD allows you to specify a preferred inactive status reason using the Merged Status Reason Value field.

To configure it:

1. Go to Advanced Settings → Customizations → Customize the System.

2. Open the Entity Configuration entity.

3. Under Forms, select the Main Form of Entity Configuration.

4. Locate the Merged Status Reason Value field and set its Visibility to Visible by Default.

5. Click Save and Publish All Customizations.

6. In your Entity Configuration record, enter the desired inactive status reason (e.g., Lost, Canceled, Disqualified).

Once set, all subordinate records merged into a master record will use your specified inactive status reason instead of the default. This ensures consistent CRM data, avoids status errors, and aligns with your organization’s customized workflow.