We are pleased to announce that the Duplicate Detection add-on now fully supports Power Apps model-driven environments, which has been requested by many of our customers.
There is an updated version of our solution available in Microsoft App Source, which has been approved by Microsoft, and is available for download.
Data Quality App – Passed New Recertification for AppSource
We are pleased to announce that Duplicate Detection Addon for Dynamics 365 has passed the new recertification for AppSource by Microsoft.
The new recertification process gives customers access to a single marketplace where they can discover certified, high-quality apps.
Certification also validates that partner apps are running on the latest version of the software, making it easier to rapidly onboard new features and capabilities.
Recertification is required each time you make an update to your app or every 6 months.
AppSource – Duplicate Detection Addon
Features for next release of Data Quality App for Dynamics 365 CRM/CE
New features
- Support for Unified Interface
- Support for Power Apps
- Source and Target filtering extended to work for Bulk Detection, List View Bulk Detection and Real-Time Detection.
- Warning of duplicate on creation of a record, for an example:
You have an DD rule on contact e-mail, when user is in process of
creating new contact and types an e-mail that is a duplicate,
duplicate warning will appear so user can see the warning before
typing all data and clicking save. - Warning of duplicate when opening a record, for an example:
If user opens a record and it has a duplicate, user will see a
warning that there are duplicate for this record.
In addition to the new features, below will be fixed:
- License user error when DD addon is installed and no rules active. It will now check for license when there is one rule active.
- Empty detection result window popping up when navigation in certain way.
Support CRM 9.x
A guick note to let you know that Duplicate Detection is now updated to support CRM 9.x and Power Apps – Model-driven.
While we are in process of getting the new solution approved by Microsoft (usually it takes 2 weeks) you can download the new package from https://dataqualityapp.com/try-it/ of by sending us a mail to support@techdio.dk
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.
Fix:
When running duplicate detection in background, the lookup field for the result was empty for easy navigation, it has been fixed in next release.
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
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” />
</filter>
</entity>
</fetch>
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: support@techdio.dk
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 e-mail:support@cowiasolutions.com
You can download latest version from Microsoft AppSource, click here
Background service released in version 2017.01
New version of Duplicate Detection Addon has been released, version number is 2017.01.
Background service has been added, it is now possible to run bulk detection and bulk merge jobs in background and foreground, the choice is yours.
‘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.
