9 posts about Webresource by 1 contributor.
Know Webresource? Share what you know with developers who are learning it.
During certain scenarios we must build a custom html to show data from Dynamics CRM as per customer requirement. As an example, a separate tab was shown on contact form to show selected contact’s Account Address details in the below use case.
During certain scenarios, we must acquire the total records count present in a sub grid. To achieve this functionality, explicit logic should be written using JavaScript with form controls that are available on the form. Contact forms with account sub grids are required, and the Contact record was used to explain this functionality.
Applications often require different configuration settings or input parameters when deployed to different environments. Environment variables store the parameter keys and values, which then serve as input to various other application objects. Separating the parameters from the consuming objects allows you to change the values within the same environment or when you migrate solutions to other environments. The alternative is leaving hard-coded parameter values within the components that use them. This is often problematic; especially when the values need to be changed during application lifecycle management (ALM) operations. Because environment variables are solution components, we can transport the references (keys) and change the values when solutions are migrated to other environments. As an example, on selected contact record an -environment variable value will be retrieved based on the schema name using webresource.
In Dynamics 365 CRM, for certain requirements we need to get users local system date time to compare with the given dates for certain business logic. As an example, on selected contact record users local date time was fetched.
In Dynamics 365 CRM, for certain requirements we need to get header values that are present in a record. We can get values with form context. As an example, on contact record form context was used to retrieve value of owner.
In Dynamics 365 CRM, for certain requirements we need to show dialog window. We can use openAlertDialog method present in Client API Reference in Dynamics crm. As an example, for a selected contact record, open dialog will be shown.
In Dynamics 365 CRM, at times we must show respective tabs based on some values of controls which were kept on form. Tabs can be shown or hidden based on the form context object. As an example, in contact form, if at all vaccination was completed then only Vaccination details tab will be shown to the user otherwise it will be hidden.
In Dynamics 365 CRM, post creation of a web resource, to use it in CRM Form for a selected entity then we must add web resource into Form Libraries present at form level and then tie it to Event Handlers for a selected Event on Main Form. As an example, in Contact Customizations Solution for Contact Entity Main Form a web resource will be added to perform customizations on Contact Record.
In Dynamics 365 CRM, any functionality cannot be achieved through OOB [Out of Box] functionality, then first thing comes into mind was customizations. So, basic customizations can be achieved starting with Web resources (js type) under code especially through JavaScript. As a business case, a new web resource will be created in Contact Customizations Solution.
DevSocialUpcoming · 3rd editionAI Agents ConferenceNov 23–27, 2026Live onlineMembers only16days leftRegisterPublish an article in this category and earn +1,000 SHARP when it is approved.
Write an article