Dynamics Community Forum Thread Details

Maximum number if conditions I can use in a business rule?

Hi Sam

In short you can have 10 Conditional Branches

Here are the full list of limitations

Business rules are intended to address common actions. Compared to what a developer can do by using form scripts, business rules have limitations. However, business rules are not intended to replace form scripts.

Here are a few limitations to using business rules:

Business rules run only when the form loads and when field values change. They do not run when a record is saved, unless the scope for the rule is set at an entity level.

Business rules work only with fields. If you need to interact with other visible elements, such as tabs and sections, within the form you need use form scripts.

When you set a field value by using a business rule, any OnChange event handlers for that field will not run. This is to reduce the potential for a circular reference, which could lead to an infinite loop.

If a business rule references a field that is not present on a form, the rule will simply not run. There will be no error message.

Whole Number fields that use the formats for TimeZone, Duration, or Language will not appear in the rule editor for the conditions or actions, so they cannot be used with business rules.

You can’t add more than ten if-else conditions in a business rule.

For Microsoft Dynamics 365 for tablets, the definition of the business rules are downloaded and cached when Dynamics 365 for tablets opens. Changes made to business rules are not applied until Dynamics 365 for tablets is closed and re-opened.

When you set the value of a lookup field, the text of the primary field value that is set in the form will always match the text that is visible in the rule definition. If the text representing the primary field value of the record you are setting in the lookup changes, the value set by your rule will continue to use the text portion of the primary field value defined by the rule. To fix this, update the rule definition to use the current primary name field value.

It is useful to understand that the value set for a lookup has three parts:

Name: The text of the primary field value you see in the form.

Id: The unique identifier for the record. This is the data that is saved. This is not visible in the form.

LogicalName: The name of the entity, such as contact, account, or opportunity.

The rule will set all three parts of this value. The Id value for a specific record never changes, but the Name value might change.

For example, if you define a rule to set a lookup to a contact that has the Full Name of ‘Old Name’, this text is the Name you will see in the lookup when it is set by your business rule even if someone later changes the Full Name of the contact to ‘New Name’. The lookup Id value will be correctly set to the expected record, but the Name (which is not saved) will reflect the rule definition value rather than the current Full Name value of the record it references.

Quick Links

Leaderboard