Frequently Asked Questions
The reason you can't see the buttons is because no ribbon customizations haven't been made.
To force them to reset you will need to do the follow steps
- Deactivate all Merge+ rules that do not have the custom merge button.
- Activate a single Merge+ rule
- Check system jobs - you will see an "Import Solution" job running. Wait for this to complete.
- Repeat steps 2 and 3 for a single Merge+ rule at a time.
- Perform a "Publish All Customizations"
If you still have issues, please raise a ticket with us at helpdesk@data-8.co.uk and we can help you.
Check with your Data8 account manager that a duplicare license has been activated for your account.
To uninstall the duplicare solution, simply follow the installation guide in reverse, removing any additions to your forms such as scripts and custom fields.
A basic uninstall process may look like the following:
1) Remove the JavaScript from any form
2) Remove the duplicate detected ID field from any form
3) Delete all your "Merge+ Rules." It is recommended doing it one at a time.
4) Delete any "Address Fields" and "Phone Number Fields".
5) Delete your "Dedupe+ rules".
6) Perform a Publish All and wait for it to complete.
7) Deactivate any active out of the box duplicate detection rules.
Once these steps have been completed, you should be able to uninstall the solution. Once uninstalled, you can reactivate your out of the box duplicate detection rules.
The data8_duplicatedetectedid attribute is used to identify records that duplicare has identified as duplicates. This is set automatically when a real-time rule is used, and is an option you can set when running a bulk Dedupe+ Job.
Records that match will have the same value in this attribute, so you can build a report by grouping records together based on this attribute.
Yes, this is to be used as part of the address standardisation option within duplicare to enable fuzzy matching on address fields. Likewise, the telephone standardisation functionality is included by default.
In general duplicare should not overly impact Dynamics performance. Checking for duplicates obviously does involve searching through the records in your database so it will have some impact, but not to the point where it should be slowing down day-to-day operations.
In general, the more fuzzy options you have in your Dedupe+ Rules, the more records duplicare will have to retrieve in order to check for duplicates. We do display a warning in the Dedupe+ Rule screen if we detect that a rule is likely to require a very large number of records to process.
Merging can affect performance. However, there is nothing different in this regard between merging using Duplicare and merging using the OOB merge options. Although we present our own user interface to make the merging process easier with multiple records, Duplicare ends up executing the same merge request(s) as if you had merged the records two at a time using the standard merge screen. If you have a large number of related records, merging can take a long time to complete.
To enable our merge process you need to create a Merge+ Rule record for the entity you want to merge. This will then import another solution in the background that contains the required changes - once this is imported you'll need to publish customizations and refresh the page for it to take effect.
The address standardization will attempt to standardize any given address but it does not provide validation at the same stage. For example if you were to input
123 High St, Liverpool, L1 1XX
I made that address up so it isn't real but the standardization would reformat like so:
123 High Street,
Liverpool
L1 1XX
Duplicare will standardize the data you provide but will not validate it. Tools such as PredictiveAddress should be used for validation.
As well as the duplicare administrator role, we will need system customizer role to help us configure.
On top of that, we will need enough permissions to perform the actions you want us to perform (i.e. if you are merging accounts, we would need all permissions associated with that - not only in account but in it's child entities etc).
Generally, if you're looking at granular permissions it can take some time to get them right which is why we always prefer system administrator. If our systems do fail with missing permissions though, we will get in touch and let you know what we are missing.
When you're going through the duplicates identified in a Dedupe+ Job you have three choices for each group:
- Merge & Next merges the records
- Skip jumps over this group of duplicates for now and leaves them for later
- Ignore discards this group of duplicates entirely and they won't be shown again for this job. You'll also be prompted to create an exclusion rule - if you do this then these duplicates won't be shown again for future jobs either
When you click the Resolve Duplicates button at the top of the Dedupe+ Job form, the merge screen will guide you through the list of duplicates that is shown in the Unsolved Groups list on the Results tab. This list can be sorted and filtered as required to limit this list for each user.
If you have two users resolving the duplicates you could choose to show all unsolved groups, have one user sort them alphabetically and another in reverse order and then both users will eventually meet in the middle.
You can also use the Assignment Strategy setting when you start the job to assign each group to the owner of the master record. This is appropriate when all your users have access to the duplicare administration app and permission to merge records, and where you have a large number of duplicates that need to be managed by the users that know those records best.
A group of duplicate records identified by a Duplicate Detection Job will be indicated as a GDPR Red Flag if there is a mismatch in the contact preferences for the records in that group. For example, if there are two contacts in the group and one is set to allow emails and the other not to allow emails, this group would be a GDPR Red Flag.
This is used to highlight groups where extra care should be taken to ensure that the correct permissions are assigned to the record during merging.
After setting up a Dedupe+ Rule with the "Real Time Enabled" option set, you also need to complete some customization on your forms to trigger the duplicate detection. On each form where you want duplicare to detect duplicates:
- Add the "Duplicate Detected Id" column to the form. It can be hidden if required or you can leave it on display and configure it to use the "Data8 Duplicates Detected" custom control to show details of the detected duplicate records
- Add the data8_duplicatedetectionscript script library to the form
- Add an event handler to the form OnLoad event. Select the data8_duplicatedetectionscript library, enter getTriggerFields as the function name and enable the option to pass the execution context as the first parameter
- Save and publish the form changes
Error Codes
You could see this error on the main configuration page for duplicare.
In order for duplicare to work, we need to have permissions into your system either as a user or an application user. If you are seeing this error, we have detected an issue when trying to connect back into your system.
Please refer to your list of connections here and the application connection does not have any errors.
You are missing a valid duplicare for this instance. Each instance requires a seperate license.
Please contact either your account manager or the helpdesk team at helpdesk@data-8.co.uk
You will be receiving this error is your Data8 username or password has changed since you initially configured the duplicare solution.
Please re-configure the duplicare solution as described in the configuration section of our installation guide.
Non-administrator users cannot merge records.
ANSWER:
The user needs a security role that includes the Merge privilege (found towards the bottom of the Business Management tab of the security role editor).
In the list of users, change the view to “Application Users”. In that list you should see a Data8 user.
I see this error when attempting to remove or uninstall the duplicare solution.
ANSWER:
To uninstall the duplicare solution, simply follow the installation guide in reverse, removing any additions to your forms such as scripts and custom fields.
A basic uninstall process may look like the following:
1) Remove the JavaScript from any form
2) Remove the duplicate detected ID field from any form
3) Delete all your "Merge+ Rules." I would recommend doing it one at a time.
4) Delete any "Address Fields" and "Phone Number Fields".
5) Delete your "Dedupe+ rules".
6) Unpublish any of your out of the box duplicate detection rules.
You will need to find these records through Advanced Find.
Once these steps have been completed, you should be able to uninstall the solution from the Solutions page.
When you have got the Duplicates Detected+ feature enabled in the solution configuration page, this error will be shown if your form includes the getTriggerFields function in the OnLoad event but the "Pass execution context as first parameter" option in the event handler is unticked.
Please see the details in the "How to enable Duplicates Detected+" section for details of how this event handler should be configured.
Errors can occur during the merge process for many reasons, but the most common two are insufficient permissions or failing plugins.
Details of any errors encountered during a merge will be displayed in the progress bar at the top of the merge screen. If the error is from a plugin, the name of that plugin will also be shown to help route any support requests to the appropriate team.
If you require support from Data8, please click the "Download Log File" link below the error and attach that to your request.