6 Business Rule Gotchas to Watch for in Microsoft Dynamics 365/CRM

With all features, there are Gotchas to watch out for.

We cover 6 common Gotchas with Business Rules in Microsoft Dynamics 365/CRM for you to watch out for …

1. Any field utilized in the Business Rule must be on the form in order for the Business Rule to run
The system will not alert you about this; it simply just won’t function the way you intended.

2. You can have up to 10 Else If Statements
Remember, an Else If statement executes a block of code if a specified condition is true.

If the condition is false, another block of code can be executed. This is part of JavaScript’s conditional statements.

3. You cannot interact with Tabs or Sections
If you are looking to do a “certain condition is met, so hide the entire section,” that is not going to work. The hiding of complete sections or tabs is better served through JavaScript.

Remember, Business Rules were intended to lessen the need for JavaScript, though there will still be a need for JavaScript in your system even when you use Business Rules.

4. OnChange events are not triggered when Business Rules set a field value
First, remember that OnChange is a JavaScript term. This gotcha is very important to keep in mind as you navigate through Business Rules in your CRM environment.

5. Whole number fields with TimeZone, Duration, or Language format are not supported
There are other ways to set these fields through workflows and JavaScript.

6. Rule definitions are cached in the mobile app
You must close and re-open the app for changes to take effect on your desktop for those you make in the mobile app.

Learn more about various processes in Microsoft Dynamics 365/CRM. Join Ledgeview for our monthly user-groups.

Get more information and register for our next user group here.

Microsoft Dynamics 365 CRM User Group Webinar