Hide Headers, Commandbar, Tabs in D365 Forms

Image
There are options available to hide Command Bar, Header part and Tabs.  Below is the screenshot which highlights these areas for your understandings. let formContext = Xrm.Page ; or let formContext = executionContext.getFormContext(); // Hide Header part formContext.ui.headerSection.setBodyVisible(false);   //Hide Command bar formContext.ui.headerSection.setCommandBarVisible(false);   // Hide Tabs formContext.ui.headerSection.setTabNavigatorVisible(false); After all are hidden,
Post a Comment

Using Resx file in D365 JS

Most of the times, we have validation or error messages to be shown to user during client side validations in D365. We directly hardcode these message in the JS functions. Instead we can use Resources file(.resx) to store all the messages in common file and use it wherever it is required.  This helps in maintaining the code and also promotes reusability. 

This file format is also supported in web resources.

Creation of Resource file:

In visual studio, resource file can be directly created as shown below.








Add the validations message as shown below and save the file(eg:UserValidationMessages). You can add as many messages you want.

Open D365 web resource and upload this file by selecting Type as 'String(RESX)' as shown below.


Below is the sample code to retrieve the messages from resource file.
  var emailValidationMessage = Xrm.Utility.getResourceString("new_UserValidationMessages.resx", "AccountEmailAddressValidationMessage");



The resource file can be updated anytime by downloading the file from webresource url as shown below.


Save the file. 

Open in Visual studio and update the message.

This file can be updated back to web resource as shown below.


This approach can also be used in multi-language supported applications where message should be shown based on the user selected language.

Comments

Post a Comment

Popular posts from this blog

Convert datetime to user local in D365 Plugins

Background: There could be times where we need to compare the datetime field with today's date in the plugin for some validations. Example: We had a requirement to compare the expiry date field with today's date.  During comparison it was not giving the expected result. In our scenario, User's timezone is in IST. In plugin, the expiry date was returned in UTC. So, if user sets the date set as 21-Oct-2021 12:00:00 PM IST, in plugin code it was returning  19-Oct-2021 12:00:00 IST and comparing with the today's date,  21-Oct-2021 12:00:00. This resulted in incorrect comparison. So, we had to convert both expiry date and today's date to user local before comparison. Following are the steps to achieve the same. 1. Get the initiating user id in plugin  2. Retrieve timezonecode from user settings entity based on  initiating user id. 3. Initiate  LocalTimeFromUtcTimeRequest by passing expiry date in UTC along with user's timezonecode to get the User's local time. B...
Read more

Using Resx file in D365 Plugins/Workflows

Image
Usage of Resx file in D365 Plugins/Workflows: Most of the times, we use fetchxml queries in the plugins and workflows to retrieve the entity data and we directly hardcode these queries in the retrieve methods. Instead we can use Resources file(.resx) to store all the fetchxml in common file and use it wherever it is required. This helps in maintaining the code and also promotes reusability. Creation of Resx File: Below is the sample Plugin project I have created to explain the usage of Resx file. Once the project is created, add new resource file named as "FetchXML.resx" as shown below. After the file is added to the project, open the "FetchXML.resx" file from solution explorer. Add the Name and Fetchxml under the value as shown below. For filter conditions, you can use some placeholders(eg: {EmailAddress}) and replace after you retrieve the Fetchxml string from resource file. Once added save this file. In the plugin code, fetchxml  can be retrieved from resource fi...
Read more

Run Power automate under modifying user context

Image
In Power automate, we can run the flow under the below mentioned user's context. 1. Modifying user 2. Flow owner 3. Record owner We had a requirement to run the flow under Modifying user. So, in the trigger we set 'Run as' Modifying user. But still we noticed it was running under the service account which we had selected in the update action and modified by of the record was always Service account. Finally, we found out that though we had selected Run as 'Modifying user' in the trigger, in every Dataverse action, we need to select 'use invoker's connection' as shown below to call CRM in the context of the modifying user.
Read more