Introduction
When integrating Power Pages with Dynamics 365, you might encounter an issue where changes to field attributes through Power Pages metadata settings do not reflect due to Dynamics 365 fields being set to read-only. This article provides a straightforward explanation and solution to this common problem.
In Dynamics 365, you can use JavaScript to retrieve the user's current geographical location and store it in custom fields on the form. This guide explains how to implement a function that utilizes the browser's geolocation API.
This guide demonstrates how to use JavaScript in Dynamics 365 to enable navigation buttons that open Google Maps with predefined locations.
Requirement
We need to limit how many records a Dynamics 365 (D365) view returns. Since there’s no out-of-box (OOB) way to do this, we introduced a custom column dsl_topn. This column holds the “Top N” value we want. A plugin then intercepts the FetchXML query and injects the <fetch top="N"/> attribute, removing any conflicting paging attributes in the process.
Below is a straightforward approach to merge two Word documents in Dynamics 365—without resorting to third-party paid connectors or extensions. By leveraging a custom Action, a Power Automate flow, and a plugin with OpenXML (embedded via ILRepack), you can seamlessly combine Word files and store the merged result, all in one out-of-the-box solution.
Working with HTML web resources in Dynamics 365 is a common way to extend forms, capture user input, and interact directly with Microsoft Dataverse data. In this tutorial, we will show how to retrieve a record ID from URL parameters and then use OData calls to fetch(Read) and Create / Update / Delete records.
Dynamics 365 Quick View forms only support a single column.
In certain scenarios, you may want to present a lookup field on a form as if it were read-only, while still allowing scripts to programmatically set or update its value behind the scenes. Here are two methods to achieve this without disabling the field entirely, thus preserving your ability to set its value via code:
Background
In Power Pages (formerly known as Power Apps portals), Entity Lists often present clickable hyperlinks on the first column. While this is convenient for navigation to detailed records, sometimes you might want to display this information as plain text instead. For example, you may have a “Case Number” or “Grievance Number” column that you want visible, but not clickable.
This guide explains how to pass parameters from a Dynamics 365 main form to an HTML web resource by enabling a built-in feature and retrieving the parameters dynamically in your HTML.
When I installed Microsoft Dynamics 365 Report Authoring Extension, got error: Action Microsoft.crm.setup.shared.analyzerbase+collectaction failed.
I followed below solution and resolved the issue.
Purpose of the Plugin
The plugin aims to streamline the user management process by automatically assigning a default web role to every new contact created in Dynamics 365. This is particularly useful in environments where new contacts need immediate and predefined access to certain parts of the system, ensuring they have the necessary permissions from the start.
Scenario
Imagine you need a report to display records based on a casemanager field that might contain null values or specific identifiers. The report should show records where the casemanager field is either unset (null) or matches any of the identifiers selected by the user from a multi-value parameter.
The Dataverse auditing feature is designed to meet the external and internal auditing, compliance, security, and governance policies that are common to many enterprises. Dataverse auditing logs changes that are made to customer records in an environment with a Dataverse database. Dataverse auditing also logs user access through an app or through the SDK in an environment.
This comprehensive guide provides a detailed approach to automate the creation of many-to-many (N:N) relationship records in Dynamics 365 using a custom plugin and a JavaScript action. The solution streamlines the association of multiple records through a straightforward interface, making it indispensable in scenarios requiring batch processing or integration tasks.
In Dynamics 365, subgrids are an essential feature that provide users with the ability to interact with related data directly from a form. In some scenarios, you may need to enhance the default functionality of subgrid buttons, such as the "Add Existing" or custom action buttons, by applying specific views or filters to control the data shown to users. This guide will walk you through the process of dynamically applying views or filters to buttons on a subgrid, providing an improved user experience.
userSettings.roles) In SQL Server Reporting Services (SSRS), customizing the date format is essential for improving the readability of reports. SSRS provides the Format() function, which allows for flexible formatting of date fields to meet different reporting requirements.
In Microsoft Dynamics 365, the customerid lookup field can reference multiple entity types, typically Accounts and Contacts. To simplify the user interface or meet specific business needs, you may want to restrict this lookup to show only one type. Below is a straightforward approach using JavaScript to configure the customerid lookup to display either only Accounts or only Contacts.
When customizing forms in Microsoft Dynamics 365 CRM, JavaScript provides powerful capabilities to control data processing and user interactions. Key among these capabilities are the client-side events onSave and addOnPostSave. Each plays a vital role in managing the lifecycle of form data submissions. This article delves into how these JavaScript events can be used to fine-tune the behavior of Dynamics forms.