Posted on

Next Release – New Features

Next Release – New Features

Here is description of new features and minor fix for Duplicate Detection Addon for Dynamics 365

1st New Feature:
For Bulk Merge, we have added the option that you can select which related entities will be merged to the master record.

For an example if you don’t want cases to be merged to the master record, you can do that now.

2nd New Feature:
Users can now run duplicate detection from list views and administrator can select which duplicate rules are enabled for list views.

For an example: User can select contacts from the view or run duplicate detection on all records from the view. User will be presented which duplicate rules are enabled for that entity and select which rule to use to check for duplicates.
From here, user can select to run duplicate detection in foreground or background as you can in current release.

When running duplicate detection in background, the lookup field for the result was empty for easy navigation,  it has been fixed in next release.


Posted on

Create Duplicate Rule That Will Ignore Integration User

This example is for those who have some integration to Dynamics CRM and already are doing duplicate detection in the integration job.

For an example, let’s say that you have integration for contacts between CRM and AX.
In the integration job for contacts, you have specified match rule when to create or update contact, let says that this match rule is the e-mail address.

If you have created duplicate detection rule on contacts and also matching on e-mail, then following will happen:

1. Integration job checks if contact exists in CRM
2. Integration job will then either create or update contact in CRM
3. Duplicate detection will also check if there are duplicate when integration job tries to create/update

If you trust the validation rules in your integration job and don’t want duplicate detection to also validate for duplicates when data comes from integration, then you can add the integration user under ‘Ignore users’ on the duplicate rule and it will ignore requests by this user.

When doing this, the following will happen:

1. Integration job checks if contact exists in CRM
2. Integration job will then either create or update contact in CRM
3. Duplicate detection will also check if there are duplicate when integration job tries to create/update


Posted on

Example – How To Select Account With Account Number As The Master Record For Bulk Merge

Here is an example how to select an account that has account number as the master record when bulk merging account duplicates.

1. First, you need to run bulk detection on accounts using one of your duplicate rules.

2. When finished, open the ‘DD Bulk Operation’ result for the bulk detection.
Here you will see all of the duplicates that it has found.

3. If you click on ‘MERGE DUPLICATES’ button, you will see option ‘Select master record by using FetchXML.’
If you check this, you are able to insert your own criteria for selecting the master record.
To use this, you need to insert the criteria as fetch xml.
For now, close the window.

4. If you are familiar with advanced find, then this will be an easy task to do.
Open advanced find, select entity ‘Accounts’ and create a filter where account number contains data and click on ‘Download Fetch XML’
Like this:


5. It will download a file ‘FetchXML.xml’ on your computer, right-click on it and open in notepad.
6. Copy all of the text from the file.
7. Go to back the ‘DD Bulk Operation’, click ‘MERGE DUPLICATES’ and check ”Select master record by using FetchXML.’
8.  Paste the value that you copied from the file.

An example of fetch xml:
<fetch version=”1.0″ output-format=”xml-platform” mapping=”logical” distinct=”false”>
<entity name=”account”>
<attribute name=”name” />
<attribute name=”primarycontactid” />
<attribute name=”telephone1″ />
<attribute name=”accountid” />
<order attribute=”name” descending=”false” />
<filter type=”and”>
<condition attribute=”accountnumber” operator=”not-null” />

9. It will now use this fetch xml for selecting the master record, if it finds more than one record for the duplicate set, it will use ‘Merge order’ options to select the master record.

Notice that it will only merge the records that are found by the fetch xml criteria, if there are any duplicates left that haven’t been merged, you can create another fetch xml to select their master record or just use the ‘Merge options’ to merge the last ones.

If you have any questions, need help with creating rules or want live demo, you are welcome to contact us on email:








Posted on

3 New Awesome Features

We are happy to announce the latest release of Duplicate Detection Addon, we have added these 3 awesome features and other improvements.
  • You can create your own rule for selecting master record for bulk merge
  • Ignore Users – You can add users which to ignore for the specific rule
  • Users can run/schedule background jobs for their own data
We have also improved many of the existing features, such as Background Service, you can now retry failed jobs and cancel them directly from CRM.
If you have questions, need help with creating rules or want us to give you live demo, you are welcome to contact us on
 You can download latest version from Microsoft AppSource, click here
Posted on

‘Background’ service coming soon


We have developed duplicate detection addon with lot of features that default duplicate tool don’t have, but we have always missed one feature, that is to run bulk detection and bulk-merge in the background/inside CRM.
Those who haven’t tried the addon by now, to run bulk detection or bulk-merge, you need to have your browser open while it is running.
This was not what we wanted to develop in the beginning but we couldn’t develop bulk detection and bulk-merg to run  “inside” the CRM because of limitations of Dynamics CRM and we have tried every workaround that you can think of.

We spend some time thinking about an external service that can run bulk detection and bulk merge, one of the questions was if we should develop it to run online/Azure or tool/service that customer can host where they want.


We have customers that are running their CRM on-premise with no internet access, on-premise with internet access and Online/365 customers.
Some customers have data policy where external access is not an option.

Because of this mix of customers, we have decided that best solution will be to develop windows service that you can install on any server, this service will connect to your CRM and check if there are any bulk detection or bulk merge jobs to run.

There will be new options when creating bulk detection and bulk merge in CRM, you will be able to schedule it and service will take care of the rest.

Release of the background service is planned in January and I will write more details when we are closer to release.



Posted on

Over 40 Features in Duplicate Detection Addon With Latest Release 1.16

I’m glad to announce that version 1.16 has been released and Duplicate Detection Addon has now over 40 features and we will not stop here.

Many features that has been added have been requested by customers, if you have an idea for new feature, we would like to hear from you.

New features:

Bulk Detection – Data Target Filtering
This feature can be used to filter records which you want to check duplicate against.
Using this feature with Source Data Filtering, you have many options how you want to detect duplicates.

Bulk Merge – Merge Options
There are more options now to select master record
You can select master record by using created date or modified date and select if it’s the newest record or oldest that is master record.


Second option is to select master record based on how many activities the record has.
You can select if the master record should be the one with most activities or one with least.

Third option is where you can select master record based on how many fields on the record has data, you can select master record with the most filled fields or least.





Posted on

Read This Before Enabling New Grid Feature in Dynamics 365


I had some time today to check out new features in Dynamics 365 version 8.2 and one of the features that I was excited to try out, is the new grid function, where you can edit data directly from the view.

Because Cowia Solutions has Duplicate Detection Addon for Dynamics CRM, I wanted to test how grid editing is working with default duplicate detection and the addon.

In my testing, I have found several issues and that is why I’m writing this blog to let you know until Microsoft fixes these issues.

Issue 1: When activating or deactivating grid feature for an entity, it will deactivate duplicate rules for that entity.
(It will not deactivate duplicate rules for the Duplicate Detection Addon)

Before enabling:

After enabling grid feature:

Issue 2:

After re-enabling default duplicate rules and if you edit directly in the grid, it will not prompt with duplicate warning if there are duplicates, for example, you have account named ‘Cowia’ and another ‘Cowiaa’, if you edit ‘Cowiaa’ to ‘Cowia’, it will not warn you for duplicate.
This is also the case for the Duplicate Detection Addon, but if you have set the duplicate rule to not allow duplicates, it will not allow the user to save and create a duplicate.

Issue 3:

When creating new record for an entity that has grid enabled, the default duplicate warning will show up but it will not show the duplicate records:

Here is example:

Duplicate warning of Duplicate Detection Addon works fine:


If you want to give Duplicate Detection Addon a try, here is link to AppSource: Click here


Posted on

Two New Features & Updated Interface

We have added two new features for Duplicate Detection Addon for Dynamics CRM.

First new feature is ‘Ignore Words’
Using this feature, you can now ignore words or letters for your duplicate rules.
For example, ignore words like Inc, Ltd, A/S, ApS, LLC
If you have record named ‘Cowia Solutions’ and other named ‘Cowia Solutions ApS’, it will detect them as duplicates.

Second new feature is for lookup fields, ‘Compare Lookups As Text’
You can now select if it should match on the GUID value of the lookup or the text value of the lookup.


Updated Interface
Interface colors and style has been updated to match the default colors and style of CRM 2016.



Many new features are planned for upcoming versions.


Posted on

Merging Quotes

Quick Post About Merging Quotes


Quote entity in Dynamics CRM is different then other entities, it is different how the status works and because of that you can’t bulk merge on all types of status.

When quote is in draft, this is the only status where the quote is still opened for editing, when status is active, the quote is read-only and can only be edited if you revise it, then it will change status back to draft.
Unlike other entities where status = active means that the record can be edited, it is different for quotes.

What it means for merging quotes, is that you can only bulk merge on quotes that are in status ‘Draft’ because the duplicate detection can’t revise the quote, merge it and then activate it again.

If you need to bulk merge active quotes, you will need to manually revise them before running  bulk merge.

Posted on

Try the addon in unlimited time

We have changed the trial policy, before you had 14 days to try the  addon
Now you can try the addon unlimited time and no license required.
You can download from here: Free Trial

These are limits until valid license is purchased:

  • Bulk merge limit up to 10 records per. bulk detection
  • One duplicate detection rule

For questions or help with setup, write to:


Posted on

Solving challenge #1 – Duplicate in Business Units

Solving challenge #1 – Duplicate in Business Units

Why is this a challenge?
Let me explain.

Default duplicate detection in Dynamics CRM can only match duplicates on those records that the user is allowed to read. It makes sense, but this can be a problem for some companies where the same record already exists in another business unit that user is not allowed to read/see.

Default duplicate detection won’t detect this duplicate and user will create a new record.

Let’s say that the record was named ‘Company A’. This record is now duplicate in the system where each record is in the own business unit.

If the users are only allowed to read from their business unit, then this is not duplicate for them. They can only see the one from their business unit. So, what is the problem?

First problem: if you have parent business unit that can read from child business units, this record will be shown twice for users from parent business unit. This would be a duplicate record for them.

Second problem: ‘Company A’ can be contacted by different users because the user didn’t know that someone is already working in this company from another business unit.

Third problem: how can the user know if there is existing record in another business unit, so the user doesn’t create a duplicate?

One solution for these problems is to use duplicate detection addon for Dynamics CRM. If you have duplicate detection addon, then it will work like this:

For this scenario, I will use the company that has HQ in Italy and offices in DK, UK, and DE. Business units set up in CRM is like this:


Louise, Abbie and Anna can only read/see data from their own business unit.
Jasmina can read/see all the data in the system.

We have the account in CRM that is named ‘Company A’. The owner is Louise, and the company is in DK business unit. Abbie and Anna can’t read/see this account because they are not in the same business unit.

‘Company A’ is an international company and for some reason, Abbie receives a call from the company. She searches in CRM but can’t find the company. Therefore, she wants to create the company and clicks ‘Save’ but the warning window pops up showing Abbie that the same record is already in the CRM, and who the owner is. She can read that Louise is the owner. Abbie will send an e-mail or call Louise regarding this phone call from the Company A. She will also ask Louise to share the account, so they work on the same account in CRM.


How was this achieved? Here is how:

You can control for each duplicate detection rule how it will detect duplicates, search for duplicates on the records that the user can read, search records that one specific user can read or scan the whole system.

Note: This is only for detecting duplicates. The user won’t be able to open records that she/he is not allowed to.

With the second feature to achieve this, you can select which view to use when showing duplicates. In this scenario, it is critical to see the owner of the record. I created a new view in CRM and added field Owner in columns, saved it as ‘Owner View’ and used it on the duplicate detection rule.


Example of settings:


If you want to try the addon, there is free trial,
sign up here: