Duplicate Detection and Decimal Fields in Dynamics CRM

Ever tried to set up Duplicate Detection with decimal fields and pulled your hair in agony? I tried to check this and found the answer under one of the threads on Dynamics Community.

Apparently, Decimal Number and Floating Number are not available for matching in the Duplicate Detection Rule under Data Management because of the Decimal Precision applied to them.

This is beautifully explained in the example below

  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 this helps

Link to the original post

CRM 2015 – Advanced find to return all enabled users with a security role

Hosk's Dynamic Blog

I had a requirement to find all the users who had a security role because I needed to update a value.

Advanced find is easy to find

I am a big fan of the advanced find and have been known to have many open at the same time

Why the advanced find is a CRM Developers best friend

In CRM 2013 Microsoft made it difficult to find the Advanced (Why Microsoft why?).  I often had to think how to find the advanced find which is a big no no in UX design (Good CRM design should not make users think)

The bad treatment of the advanced find caused one CRM developer to create a solution which added the advanced find to every record

CRM 2013 Tool – Advanced Find on record forms for CRM 2013

Security Priviledges

If you have users who don’t have security roles you will…

View original post 394 more words

Using Advanced Find and Linking to a Subject Tree.

Advanced find is a boon for CRM and with CRM 2015 it’s got now even better.

Let’s suppose that you have a Subject Tree which further categorizes subjects of Case. As we all know that subject tree has a parent subject and then child subjects underneath the parent. Hence a case can have Subject of the Parent Category or child category in the Tree.

Prior to CRM 2015 it was a pain to find Cases that had Parent or child from the Subject Tree for reporting purposes using advanced find.

Real time scenario: Let’s assume that Subject Tree is set as parents to “X” and there are sub categories as “A”, “B”, “C” & “D”.

Now you can do this by creating a link to the subject, and looking for subjects UNDER the parent. Now that the subject tree is a hierarchy, the UNDER condition will return all children of the parent specified in your advanced find query. Screenshot attached below:-


You can further group them as an OR condition, and then you’re good to go.

Hope this helps.

{Quick Tip} When to Pick Option set and Lookups in Dynamics CRM

Reblogging… Thanks!


This post is on when should we use Option set (Pick list field) and when we should use Lookup field in Dynamics CRM when it comes

to using them for making choices, i.e., the end users need to be given a choice of options or a selection.

Working on different projects across different clients, geographies, consultants and developers- I still notice that

people have a tendency to choose this types differently Some example are:

· Category

· Sub-Category

· Territory

· County

· Town

· Country

The list can keep growing.

So, my blog’s main focus is to understand when to pick what:

· Option set Fields:

Ø This should be picked when the number of option set values are smaller (typically up to 10 values).

Ø This should be used when there are not many changes required to the values or new additions to the possible

values is not…

View original post 232 more words

Converting Activity to Opportunity, Customer not Pre-Populated in Dialog Box.

Ever wondered that when you try to convert a phone call to an opportunity why you have to search the customer in the look up option where as you wanted it to be pre populated. However the field is blank at times when you click on convert opportunity.

The reason it happens cause when you click on Convert to opportunity on phone call page, it tries to map “call to” field on the page to auto populate the “customer” field in the dialog box when you click on convert to opportunity. So if the Call to field is mapped properly the customer will be mapped and auto populated.

Also note that while converting to opportunity from Appointment, it uses the required field for the same.

Hope it helps!

Solved: You cannot change your own access mode!

If you are a system administrator, have you ever tried changing your access mode? If you try to change the access mode you will get an error as follows.


If you will check the log file it says “You cannot change your own access mode. Contact another System Administrator”

So even if you are an administrator, you cannot change your Access mode and you would have to get in touch with another System Admin who can change it for you.

Guess it’s another good reason to have more than one system admins. 😛

Hope it helps!

Overcoming Multi-Level Rollup Field Limitation

Work and Study book - Dynamics 365(CE) & Power Platform Blog

Currently I’m working on a project that has some scenarios that need to do rollup calculation in 3 or more level of relationship hierarchy. For a sample and imaginary case, I have an entity called Project that has one or more Project Milestones and each Project Milestones has one or more Invoices (Project 1 – N Project Milestone, Project Milestone 1 – N Invoice). And I would like to see the total paid invoice value at the project level so that the project manager could have a quick overview on the project budget vs invoice that has been paid. To achieve this, the first thing that come up in mind would be the new Rollup Field that introduced in Dynamics CRM 2015.

However, there are some limitations of rollup field: “A rollup attribute formula can’t reference another rollup attribute.” and “Rollup attributes can’t be used as a workflow event or wait condition. These attributes…

View original post 367 more words