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

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) / difference and limitat...
Microsoft Dynamics CRM (Archived)

difference and limitations between Calculated Field and Business Rules?

(1) ShareShare
ReportReport
Posted on by Community Member

I am unable to find a straight clear answer with comparisons between calculated fields and business rules.

I am looking for limitations, differences, in what situation would I use one over the other???

Website references, straight answers, whatever. Please explain. Thanks much,

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Vinicius Drumond Profile Picture
    Vinicius Drumond 70 on at

    Hello Adam,

    The difference between the Calculated Field and Business Rule are as follows:

    - Calculated Field can be used to make calculations in the current entity or related entities controlling.

    The calculations can be made in the Business Rule.

    - Business Rule serve as a JavaScript, but do not use FetchXML to filter to other entities.

    It can be used to set values, visibility, leaving a required field ...

    The link below has a very practical example of how to use calculated fields:

    technet.microsoft.com/.../dn832103.aspx

    I have helped.

    Att.

    Vinicius Drumond

  • Verified answer
    Robert Wittig Profile Picture
    Robert Wittig 1,885 on at

    I would take a look at this article, it provides a nice matrix to three different ways to calculate fields.

    www.crmconsultants.co.uk/business-rules-vs-rollup-fields-vs-calculated-fields

  • Suggested answer
    ScottDurow Profile Picture
    ScottDurow 21 on at

    For what it's worth - another big difference (other than the fact that Business Rules are implemented using Javascript on the client and Workflows on the server) is that Calculated fields are created using a SQL Server Calculated Column and so cannot store any data and always will be evaulated when requested using the current formula - where a business Rule is applied on-top of an existing attribute and so can store historical data.

    Hope this helps

  • Community Member Profile Picture
    Community Member on at

    Thanks guys. The above information helps a lot!

  • Community Member Profile Picture
    Community Member on at

    can we get difference of three fields in calculated fields??

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
JS-09031509-0 Profile Picture

JS-09031509-0 3

#2
AS-17030037-0 Profile Picture

AS-17030037-0 2

#2
Mark Eckert Profile Picture

Mark Eckert 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans