We can make use SuppressDuplicateDetection optional parameter of the Request if we want the configured duplicate detection rules to run and throw an exception while creating or updating the record. We will use the below out-of-the-box duplicate detection rule, that checks for lead having same email address. Below is our code and we can see … Continue reading “Use SuppressDuplicateDetection…
Continue Reading Nishant Rana’s Article on their blog
Use SuppressDuplicateDetection parameter of Request to throw an exception in case of duplicates – Dataverse / Dynamics 365
We can make use SuppressDuplicateDetection optional parameter of the Request if we want the configured duplicate detection rules to run and throw an exception while creating or updating the record. We will use the below out-of-the-box duplicate detection rule, that checks for lead having same email address.
Blog Syndicated with Nishant Rana’s Permission
More About This Author
Array
- Dyn365CE7 May 2024Use Filter Array action to remove values from an array variable – Power Automate
- Dyn365CE6 May 2024Fixed – The latitude or longitude for the User record associated with this resource is invalid – Dynamics 365 Field Service /Dataverse
- Dyn365CE30 April 2024Use Geolocation Settings for Location Tracking and Auditing – Dynamics 365 Field Service
- Dyn365CE29 April 2024Fix the trigger – Microsoft.OData.ODataException: A binary operator with incompatible types was detected. Found operand types ‘Edm.Guid’ and ‘Edm.String’ for operator kind ‘Equal’ (Power Automate / Dataverse)