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

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

difference and limitations between Calculated Field and Business Rules?

(1) ShareShare
ReportReport
Posted on by

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
    70 on at
    RE: difference and limitations between Calculated Field and Business Rules?

    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
    1,885 on at
    RE: difference and limitations between Calculated Field and Business Rules?

    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
    21 on at
    RE: difference and limitations between Calculated Field and Business Rules?

    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
    on at
    RE: difference and limitations between Calculated Field and Business Rules?

    Thanks guys. The above information helps a lot!

  • Community Member Profile Picture
    on at
    RE: difference and limitations between Calculated Field and Business Rules?

    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

Responsible AI policies

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

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
Community Member Profile Picture

Community Member 2

#1
HR-09070029-0 Profile Picture

HR-09070029-0 2

#1
UllrSki Profile Picture

UllrSki 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans