In Microsoft Dynamics 365 the creation process when creating a business rule is significantly different, in a good way! The business rules still use programming logic in a more visual and simplistic manner. Business rules are more than just business logic, they are extremely useful, and can be used to lock fields, hide fields and display errors on fields. I will walk through how to create a business rule to ensure that the end date for an event is after the start date, and to display an error message next to the field if it is not.
Initially there’ll be a condition with no rules applied to it. I then created two rules to be used with an ‘and’ conjunction (Rule Logic) which means they both must be true for an action to occur.
Above you can see that the finish date must be less than (before) the start date and that the finish date must contain data. The finish date must contain data so that the error isn’t displayed when no data has been entered in the field. In the red box, there’s a nice view which displays the logic once it has been implemented.
Next, there’s an action that occurs when both conditions have been satisfied. In this case an error message is displayed that is shown in the below image. An action can be added to a condition by dragging the action from components to the right of the condition. Adding an action below the condition makes the action an ‘else’ action.
This shows the simplicity when creating business rules in Dynamics 365, it is easy to pick up, edit and implement.