DYNAMICS 365 HOW TO DISABLE FIELDS AFTER RECORD CREATION - NO CODE SOLUTION

Last day, I had a task that requires to disable some fields on the form after the record is created.

As a developer, you might directly thought in JavaScript; but, there is an easier and faster way to do it with no code needed, Business Rules.

In this post, we will see how to disable fields after the record creation using Business Rules

Below are the needed steps to achieve this need

  1. Go to the specific entity and create a new business rule
  2. In the Condition element, choose a field that it will always be filled once the record is created (created on, modified on...)
  3. Add the condition if the chosen field Does Not Contain Data => record not yet created (Modified On Does not contain data, Create On Does not contain data...)
  4. In the True part of the condition, add the Lock/Unlock element for the field you want to Enable and repeat it to all the necessary fields
  5. In the False part of the condition, add the Lock/Unlock element for the same fields and choose to Disable the necessary fields
  6. Set the rule scope to All Forms and Activate it
    Disable Enable fields in Business rules 1

  7. When you click New button, you will be able to enter values in the fields
    Disable Enable fields in Business rules 2

  8. After the record is created, the fields will be locked and you will not be able to modify them
    Disable Enable fields in Business rules 3

Bonus Tips:
  • You can choose built-in fields as well as custom fields. Personally, I prefer built-in field such as Created On, Modified On...
  • Make sure that all fields that are used in the Business Rule are placed on the form
  • To speed up the business rule creation, you can copy/paste the components as detailed in my previous post

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