FAQ'S

DQ for Dynamics™ is a data cleansing tool (plug-in) which works inside Dynamics 365 to ensure the data in your CRM system is duplicate free. It allows you to review two or more duplicate records side by side and then create a surviving “Golden Record”.

DQ for Dynamics™ can cross compare records from Lead entities to Account or Contact entities. This allows for a complete and accurate Single Record View to be created.

DQ for Dynamics™ is straight forward to set up and we can usually have you up and running within a couple of hours.

DQ for Dynamics™ allows users to fully automate the following steps:

• Matching
• Best Record Detection
• Best Field Detection
• Merging

This allows users to save time and money. Please see Display & Auto Fill.

DQ for Dynamics™ is installed by running one executable. Once installed, DQ for Dynamics™ will appear as a plug-in with your CRM application. Please see our Installation Guide for more information.

Your data remains secure in your CRM system. Our Managed Plug-in securely sends Phonetic match tokens via SSL to our DQ for Dynamics™ Servers when Online or IFD.

DQ for Dynamics™ is licensed on an annual license basis. It’s price scales depending on the number of records you hold in your CRM system.

• More than two records can be reviewed at the same time for manual review
• Multiple data stewards can review, defer and re-assign reviewer ownership
• Master (Best or Golden) records are created and maintained manually or by rules
• The Master record from any duplicate set can be promoted manually. Or, through configurable rules, each duplicate group or all duplicate groups.
• The Master records fields can be auto-filled using configurable rules manually. Or, through configurable rules, each duplicate group or all duplicate groups
• Auto-merge of records can be configured to avoid reviewing of identical duplicates
• Ease of use – Pre-defined templates and wizards help the user define sessions with ease
• Control – Flexibility in matching, reviewing and processing puts the user in control
• Speed – Matching and reviewing is fast and can be automated for speed
• Security – Data remains in your system for security
• Powerful – Advanced matching, review and Master record Merge (MRM) Rules ensure that P&M compared to the out-of-the-box duplicate detection is much more powerful

DQ for Dynamics works with all deployments, Dynamics 365 Online, On-Premise and IFD.

Note: For On-Premise installations, our DQ for Dynamics™ Web Services application will need installing.

DQ for Dynamics™ has the ability to process large amounts of data, and has the capability to process millions of CRM entity records.

Yes, we can provide a trial of DQ for Dynamics™ where you can test it’s functionality before you purchase. 

Please contact us directly if you would like a live demonstration of the DQ for Dynamics™ tool or you would like to “try before you buy”. 

For this, we can allow up to 5 matching sessions, and you can review 10 duplicate groups using the trial version.

Reading of Data from CRM

• Data is retrieved from our hosted secured Server through service call with https connectivity.
• RetrieveMultiple Method is used to retrieve Database. (https://msdn.microsoft.com/en-in/library/microsoft.xrm.sdk.iorganizationservice.retrievemultiple.aspx)

Storing retrieved data into a temporary Database

• To process data into our Match engine, we need to store data in temporary Database.
• The database is password protected
• The field values are Encrypted
• Once fed to the Match engine, the temporary Database is deleted

Data disposal

• Except for the above temporary encrypted data store, any data is retrieved from live for review, using the UniqueId (GUID) and then disposed

Passing data to Match engine

• Data from the temporary database is processed by the Match engine,
• Once used, the temporary Database is deleted
• Only the Matching record Unique Id’s (GUID’s) are permanently stored in a results list database for subsequent processing.

Review Processing

• The session result list GUID’s are used to retrieve data for review

Obfuscation & Encryption

• All DQ Global source code is protected by SmartAssembly (https://www.red-gate.com/products/dotnet-development/smartassembly/)
• Data Encryption uses the SymmetricAlgorithm. (https://msdn.microsoft.com/en-us/library/system.security.cryptography.symmetricalgorithm(v=vs.110).aspx

DQ for Dynamics™ uses a drag and drop interface and a session set-up wizard, which will be familiar to Dynamics 365 Users, however, if required we can provide training. 

We recommend a 4 hour online training session to help get you up and running, normally broken up into 2 x 2 hour sessions. After this, we are always here to help and support. 

You open the DQ for Dynamics™ tool within your CRM application and use the drag & drop to perfect the master record. Please refer to our Create Session Overview page for more information.

The DQ for Dynamics™ tool is fully optimised using the latest technologies and will perform matching, mastering and merging of records with incredible performance. Specifics of performance depend upon, internet speed, the number of fields being processed, the rules applied to those fields etc. As such, we encourage you to take a trial and try before you buy.

Currently, DQ for Dynamics™ can be integrated with Microsoft Dynamics CRM versions from 2011 and above.

We also have capability to integrate with Workbooks CRM, please reach out to us directly should you run on this CRM. 

We welcome enquires from all CRM Users, whichever CRM system your business runs on. We have other products available which can offer a range of solutions that may well benefit you.

We are keen to make sure your user experience is a good one. Annual License fees includes full support for the software. You can email us on support@dqglobal.com or call us directly, we are committed to resolving your issues or queries as soon as possible.

Yes, we provide a range of capabilities to help with fuzzy matching of records, including:

• Homonyms, Synonyms & Aliases
• Pre-built data transformations in 13 data categories and 5 spoken languages
• Phonetic algorithms in 5 spoken languages
• Deterministic and/or Probabilistic matching

Please view our Transform Guide for full details.

Yes, you choose the scoring and weighting thresholds to determine when a record is identified as a duplicate.

You can define configurable rules from our – ever expanding – list, to determine how values from duplicates will autofill any Single Field, or Field Group to perfect your chosen “Master Record”.

You can define from our – ever expanding – list of rules to identify your “Master Record” from any group of duplicates.

Yes, auto-merging of identical records is possible. You select the Entity fields you wish to be compared and DQ for Dynamics™ will save you time reviewing identical records.

Referential integrity is maintained because we make all of our merge calls through the CRM SDK to ensure all linked data is correctly re-assigned from any duplicate record to the surviving “Master” record.

Duplicate records are queued until our Merge Service Runs, at which time, all duplicate records are de-activated and any data linked to a duplicate is moved from the surviving Master (Best) Record.

Yes, you can create multiple user accounts in DQ for Dynamics™ and assign data stewards’ permissions as administrators or reviewers. Administrators are able to create sessions and edit them; Reviewers are only able to review sessions.

DQ for Dynamics™ has the ability to match data in 5 spoken languages: English, German, French, Italian and Spanish.

Data transformations and Phonetic rules are available in all languages.

Yes, you can use your Personal / Shared / System views from CRM to select which records you wish to process for matching.

Yes, you can use popular phonetic algorithms like: Soundex and Metaphone; or you can use our advanced Phonetic algorithms: DQ Fonetix™, DQ Metaphone™, DQ Soundex™ for significantly better match results.

Yes, it is possible to sub-set a duplicate group. This can be helpful if you find more than three duplicates, and there are two or more duplicate groups you wish to split into sub groups.

We do not provide an ability to export a report, however, DQ for Dynamics shows a summary of results in the Match Session review screen.

There is a custom-built, comprehensive library of data transformations. These cover 13 data categories and 5 spoken languages.

You can even build your own if you wish and use them in DQ for Dynamics™.

You can set up rules for: Auto-Promote, Auto-Accept, Auto-Fill and Auto-Merge and save reviewing and processing times.

Yes, any custom fields will be displayed and can be used in any match session.

Yes, any non-duplicates can be suppressed either permanently from all future match sessions or for the specific session being reviewed. Any record that has been permanently suppressed will not re-appear in a future match session unless it is newly found against another different record.

Yes, DQ for Dynamics™ links directly to the CRM database using the Dynamics CRM SDK to read write and merge records in the CRM database. There is categorically no need to export your data and send it off site, your Data remains secure in your CRM system.

Sometimes DQ for Dynamics will not load in your CRM Instance. This may be due to regular updates. The solution to this is to clear your cache on your browser and then refresh your screen (Ctrl + F5). 

Once a user has been provisioned, a services account (at no extra license cost) can be used to connect to your instance. This will prevent lack of access to the account if a User Admins leave the business.

DQ for Dynamics gains access through user accounts, therefore if there is a MFA installed, it will be unable to continuously remain connected. Therefore, you must generate a static App password which can be used for connectivity.

Please follow the steps outlined in the guide below.

https://support.office.com/en-gb/article/create-an-app-password-for-office-365-3e7c860f-bda4-4441-a618-b53953ee1183

To ensure consistent availability and performance for everyone, Microsoft applies some limits to how APIs are used. These limits are designed to detect when client applications are making extraordinary demands on server resources. Below are some common measures implemented.

Further information can be found here.