DYNAMICS 365 BUSINESS RULES LIMITATION WITH MULTISELECT OPTION SET FIELD

Since the introduction of the Business Rules as a new functionality in Dynamics 365, it becomes the recommended way to be leveraged against writing client-side code whenever it is possible.

By using this approach, it will become more maintainable and supportable for further upgrades of the environment and will reduce time spent on code management and compatibility before/after the updates.

However, there are situations where you cannot fully apply your needs in a Business Rules due to the complexity of the need or limitation in the Business Rules. Therefore, you have to get back again to JavaScript.

In this post, I will talk about one of those limitations in Business Rules which is related to Multiselect option set fields.

Unfortunately, when you have a multiselect option set field, you cannot use it as part of the Business Rule condition or within the available actions, even if you want to achieve a simple task like showing or hiding it, you will not find it within the fields list.

multiselect option and business rules

multiselect option and business rules 2

Luckily, you can overcome this situation by adding a JavaScript function in order to achieve what is needed against the multiselect option set field.

For example, if you want to show the field, you can do it as you normally do with any other field by adding the following line of code on the specific event you want to execute formContext.getControl("cak_paymentmethodecode").setVisible(true);

In order to have a look on the different elements and possibilities of the business rules, you can check this docs link.

Finally, if you find that this feature should exist in the business rules, you can vote on the idea in this link.


Hope This Helps!

Comments

Post a Comment

Popular posts from this blog

DYNAMICS 365 HOW TO HIDE RECENT RECORDS FOR LOOKUP FIELD IN UCI

Image
In UCI, a lot of behaviors have been changed comparing to the Classic Web Interface such as the tabs, BPF, and many others. Today, I will be talking about one of these behaviors which is the Recent Records in lookup fields. In a brief summary, the Recent Records feature will suggest the latest records that have been searched for, where the user can select one of them, and, the list of available records of the current view will then be displayed. This is a nice-to-have feature since it might help the users to speed up data entry. However, if the lookup has been filtered to display specific records, the Recent Records will not respect this filter and will keep showing records even is they should not. This scenario can lead to selecting a record by the user that is not allowed to be selected. Therefore, in this situation, it is better to hide the Recent Records t
Read more

SEARCH BY GUID IN DYNAMICS 365

Image
Is it possible to search for a CRM record using its GUID ? Well, NO it is not possible and YES it is possible!!! As always has been, it is not possible to search for a record by its guid in Advanced Find and in the Quick view search. However, in the model-driven app Edit filters functionality, it is possible to search for a record by its Guid. How it works, let's check the 3 different places where we can search for a records. Advanced Find search Using the Advanced find feature, you cannot put a GUID value to search for. You will directly receive an error notification eventhough when you download the fetchXml, the Guid of the record will be there. Quick view search Using the search box
Read more

SAVE FORM IN DYNAMICS 365 JAVASCRIPT

Image
In Dynamics 365, you may need to save a CRM form automatically in JavaScript upon a specific action on the form. In order to do that, the function formContext.data.save(saveOptions).then(successCallback, errorCallback); can be used to save the record asynchronously with callback functions to be executed after the save operation is completed. The following example will display a successful message if the save operation is completed, and a failure message if not. formContext.data.save(1).then( function () { alert("Successfully Saved!"); }, function () { alert("Failed while saving!"); });
Read more