DYNAMICS 365 DISPLAY LOADING PROGRESS INDICATOR ON FORM

Most probably, you have faced a scenario where you need to block the user from interacting with the form and you want him to wait a little bit until a process is completed and then he can work again on the form.

However, blocking the user from working without informing him that something in the background is being processed is not a pretty thing to do.

Therefore, and to avoid this misunderstanding, you can display a loading dialog to inform him of this behavior, so he knows that he should wait a little bit before resuming the work on the form.

To achieve this, there is a straight forward method to do it, which is by using the Xrm.Utility.showProgressIndicator("Processing... Please wait!!!") method in the JavaScript.

You can add this line of code in any function, where you want to block the user from interacting with the interface while you are waiting for a process to be completed. Once the process is done, you can then remove the loading dialog and the user can resume his work on the form.

Furthermore, to remove the loading dialog, you can use the method Xrm.Utility.closeProgressIndicator().

The loading process dialog will look as in the below picture with the message you defined as parameter. Loading progress indicator


Bonus Tips:
  • To update the displayed message in the loading dialog, you can simply do another call to the method showProgressIndicator and the message will be overridden with the latest text specified in the latest method call
  • The progress dialog will block the User until it is closed by the call of the method closeProgressIndicator
  • The method closeProgressIndicator will do nothing and will not affect the User Interface if there is no progress dialog currently displayed

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