Business Rule functionality was a welcome addition to the arsenal of customization tools in Microsoft Dynamics 365. It allows greater flexibility on entity forms without the need to completely rely on JavaScript development. However, there are some less known pitfalls that may leave you scratching your head wondering why the Business Rule you created had no effect.

In this blog, we share a list of “gotchas” for Business Rules in case you are stuck.

JavaScript interference

Before designing a Business Rule for a particular entity, make sure to check if any existing JavaScript on the form will interfere with your Business Rules. JavaScript may accidentally trigger your Business Rules prematurely or cause other unexpected behavior. If JavaScript already exists on the form, it may make sense to continue leveraging JavaScript instead of Business Rules to manage behavior on the entity form. This can avoid any conflicts from the get-go, but it may also be easier to support going forward since all the behavior is managed in one place. Just remember to take into account the expectations of form behavior for users on mobile devices.

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.

Conclusion

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!

Avatar for Joe D365

Joe D365

Joe D365 is a Microsoft Dynamics 365 superhero who runs on pure Dynamics adrenaline. As the face of PowerObjects, Joe D365’s mission is to reveal innovative ways to use Dynamics 365 and bring the application to more businesses and organizations around the world.