Troubleshooting
Troubleshoot Plauti Deduplicate for Dynamics 365, including setup, publishing, permissions, form handlers, matching methods, results, licensing, access, and uninstall dependencies.
Job results state result fields not configured
Configure Result Fields for Duplicate Check and Cross-Entity job results to display record data, then save and publish settings for the relevant entity or match entity.
Fewer duplicates found than expected
Learn why Duplicate Check may show fewer matches than expected and how Entity Settings determine which active or disabled records appear in results.
DC Local - Users cannot access app
Learn how to grant organization-wide administrator consent in Azure so users can access DC Local without consent errors.
Cannot uninstall because of dependencies
Learn how to resolve dependency errors when uninstalling Duplicate Check by tearing down setup for all entities before removing the solution.
Cannot publish entity for the first time
Troubleshoot first-time publishing failures by checking whether another entity is being published and waiting 5–10 minutes, or verifying that you have a Power Automate license.
Default entities not installed
Learn why default Contact, Account, and Lead entities may not appear in Duplicate Check for D365 and how missing Power Automate licensing can affect setup and scenario publishing.
Cannot select all matching methods
Learn why lookup fields, such as Company Name in Contacts scenarios, only support the Exact matching method and cannot use other matching options.
Duplicate Check does not seem to work
Troubleshoot Duplicate Check by verifying permissions, handlers, entity and notification settings, publishing status, and form setup, with steps to resolve stalled or failed publishing processes.
Enable asynchronous form handlers
Enable asynchronous onload and save handlers in every Dynamics 365 app where Duplicate Check should detect duplicates, then save and publish the app settings.