top of page
  • William Wenzel

Dynamics CRM Tech Tip – Conditionally Show and Hide Fields on an Entity Form – Part 3

In our previous tech tips we have described how to implement showing and hiding logic using business rules and custom JavaScript. It is important to understand when to use business rules versus custom JavaScript and vice versa. Choosing the correct method to implement your showing and hiding logic can help cut development time and save on maintenance costs.

Business rules are great for very simple logic that needs to be applied across a small number of fields. Business rules have a lower maintenance cost because they do not require code to be written and do not require a developer to implement. They are also easier to edit using CRM’s built in editor rather than having to open an IDE to edit JavaScript and re-upload code.

However, because business rules are limited and cannot support complex logic, custom JavaScript will need to be used in some cases. The benefits of using custom JavaScript is that you have complete control over the form through the Xrm.Page object model and can implement powerful logic to drive your showing and hiding rules. The drawback to this is that code can become complex and difficult to maintain compared to business rules. If you are implementing a lot of showing and hiding rules using JavaScript, it is highly recommended to abstract the showing and hiding mechanisms into utility functions.

bottom of page