In this blog, we share a list of “gotchas” for Business Rules in case you are stuck.
OnChange behavior is not triggering
Do not use Business Rules to trigger an OnChange event. This is by Microsoft’s design, so the system does not accidentally get lost in an infinite loop.
Mismatch of field properties
If you have a Business Rule that is supposed to take a field’s value to update another field, it may not work. There may be no obvious indication of why it didn’t work (e.g. error message).
In this scenario, check the properties of the fields in question. If there is a mismatch in field data type, or if one field does not match the field length of the other, then the Business Rule will not work. Simply update one of the fields to match the other field’s data type and length and test the Business Rule again.
Check if all fields are on the entity form
If you are encountering issues with your Business Rules, it makes sense to check if all the fields involved in the conditions are present and published on the entity form. This may happen in a scenario where you are hiding a supporting field that shouldn’t necessarily be displayed to the user.
Check the scope of the Business Rule
Make sure to verify the scope of the Business Rule before activating it. This setting can be found in the top right corner of the Business Rule creation window. There may be scenarios where you do not want the Business Rule to trigger for multiple entity forms.
Hopefully the above tips may have resolved an issue with your Business Rules. Be sure to share your tips in the comments below if you have any other experiences with Business Rules!
For more helpful Dynamics 365 tips, be sure to subscribe to our blog!
Happy Dynamics 365’ing!