web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Decimal Fields and Dup...
Microsoft Dynamics CRM (Archived)

Decimal Fields and Duplicate Detection

(0) ShareShare
ReportReport
Posted on by jbonomo 380

I have what is hopefully a simple question pertaining to duplicate detection. I was recently trying to setup a duplicate detection rule which would have one of its conditions be a decimal field. I was unable to select the decimal field. It looks like all other data types (atleast the ones my organization uses, lookup, single/multiple line of text, whole number, date time, lookup) are able to be selcted. Why are decimal fields not allowed to be used in duplicate detection rules

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Mithilesh Kumar Profile Picture
    Mithilesh Kumar 10,047 on at

    Hi Joe,

    Decimal Number and Floating Number are not available for matching in the Duplicate Detection Rule under Data Management.

    This is because of the Decimal Precision applied to them.

    There are two places where Duplicate Detection Rule comes handy, One when you saving the record from the view and other when you are exporting.

    Duplicate Detection Rule gets fired before the actual data is saved.

    Lets consider an example

    1. You have a form with a Field whose Data Type is Decimal Number and Decimal Precision is 2

    2. You save a record with a value 10.10 in the field

    3. Now, when you create a record you put 10.1 in the field and hit save

    4. Suppose there was a Duplicate Detection Rule involved this condition would fail as 10.10 and 10.1 would have not been an exact match, but when the document is saved it will save the value as 10.10 (since decimal precision is 2) and hence Duplicate Record.

    5. Same thing would have happened when you tried to import records to the system. The condition would have failed.

    Hope that makes sense

    Thanks

  • jbonomo Profile Picture
    jbonomo 380 on at

    Great explanation! Makes perfect sense. Thank you.

  • Community Member Profile Picture
    Community Member on at

    I have a related question.  Can I use a two option (Yes/No) option set in duplicate detection rules?  I have a bunch of Accounts that have a "type" stored in a set of two options sets - isCustomer, isSupplier etc.  I want to do a name match but only for those records with the same type.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans