Situation

Currently the duplicate Detection Rule throws a warning when a duplicate is recognized. The User then may decide to accept or to ignore following the warning to create or not to create the duplicate record.

Problem

The creation of a duplicate is not really prevented. In some situations the creation of a duplicate record is required to not be allowed, means to be blocked by the system as duplicates in the system will bring up problems in system usage, like e.g. Power Automate Flows that may run into errors or insufficient data quality issues.

Idea

Enable Duplicate Detection Rules to be configured in its behavior. Let Duplicate Detection Rules be set up to either act as currently implemented and let the user decide to create a duplicate record or to accept the warning or have the Duplicate Detection Rule actively prevent the creation of a duplicate record. The prevention of a duplicate creation then also be combined with a custom information text to specifically tell the user why the duplicate record creation is prevented.

Benefits

1. The data quality may get much better for many customers.
2. Creation of Plug-Ins, APIs, Power automate Flows may get less complex as duplicate creation is already prevented where it should be, while its detection.
3. With having a custom Duplicate Detection information text, users may get better understanding about the current situation and the informing text also may be more business oriented for the user.
4. System customization may get much easier, especially in regards to data quality.
5. ... and perhaps many other benefits not yet in my mind.