Creating a Custom Button on a Main Form Using Ribbon Workbench in Dynamics 365
In Dynamics 365, tailoring the user interface according to specific business processes enhances user experience. This guide demonstrates how to create a custom button on an entity's main form. This button has conditions for visibility and will execute a specific JavaScript action when clicked.
When working with SQL Server Reporting Services (SSRS) in Dynamics 365, you might come across a peculiar issue where the metadata doesn't appear as expected, or the CRM Login pop-up window fails to display the list of available organizations, even when the option "Display list of available organizations" is checked. The root cause could be the credential settings in the data source of your SSRS project.
This article will introduce how to install the SSRS template of Visual studio before you start to create your first SSRS report for Dynamics 365/CRM/CE.
Introduction: When working with SQL Server Reporting Services (SSRS) in conjunction with FetchXML queries, you might encounter a scenario where date/time parameters cannot be used directly. This article outlines a practical solution to convert date/time parameters to text type, enabling their use in FetchXML queries within SSRS reports.
When working with date-only fields in Dynamics 365, displaying the correct local time can be a challenge. By default, Dynamics 365 stores DateTime fields in Coordinated Universal Time (UTC). This article explains how to set a date-only field to display the local time using N52 formulas.
SetLookup FunctionIn Dynamics 365, Lookup fields often need to be set programmatically, based on certain conditions or actions. One common requirement is to set a Lookup field to a specific entity based on its GUID. The N52 formula engine provides the SetLookup function to meet this need efficiently. This article will walk you through how to use SetLookup to set Lookup fields in Dynamics 365.
When working with N52 formulas in Dynamics 365, you might need to display the name referenced by a Lookup field or the name of a selected option from an Option Set field. This article aims to guide you through these tasks using N52 formulas.
When working with Dynamics 365, the term 'Intersect Entity' might come up when dealing with N:N relationships between entities. This article aims to explain what an Intersect Entity is, how to find its schema name, and how to query it using tools like XrmToolbox.
This updated article focuses on modifying the "Primary Navigation" in a Dynamics 365 Portal. This is an out-of-the-box Web Link Set that controls the main navigation menu. You will learn how to update existing links or add new Child Links to customize your portal's navigation.
Introduction: Power Apps portals offer remarkable flexibility in displaying and managing data. However, sorting columns from related tables in a list isn't straightforward. This article introduces a solution to enable this functionality.
Power Apps portals offer a robust platform for building interactive web applications. One of its most notable features is the ability to create custom search filters using FetchXML. In this article, we'll explore how to use FetchXML for search filters, leverage JavaScript for UI adjustments, and examine the behavior of the "like" operator in FetchXML.
Dynamics 365 and Power Apps offer extensive customization options, one of which is the ability to use subgrids to display related records. While subgrids are helpful, there are scenarios where you might need to prompt the user with an alert if the subgrid is empty. In this article, we will discuss how to achieve this functionality using JavaScript and jQuery.
Changing the height of HTML elements is a common requirement in web development. This can often be achieved using CSS, but sometimes it requires a little more effort—particularly when dealing with iframes or other embedded content. In this article, we'll examine a specific case study that deals with adjusting the height of a Quick View form in Dynamics 365, a Microsoft product commonly used for CRM.
Option Sets, also known as Choice fields in the latest version of Dataverse, are commonly used in Dynamics 365 to allow users to select from a pre-defined list of options. In some instances, you may want to set a default value for an Option Set (Choice) when a form is loaded. This can be achieved using JavaScript. Below are examples for both single-select and multi-select Option Sets (Choices).
Creating a dynamic user interface is a critical aspect of application development in Power Apps Portal. One common use case involves conditionally showing or hiding UI elements like buttons based on certain criteria. This article will guide you through the steps to dynamically hide a "Create New" button in a subgrid when certain conditions are met, using JavaScript and the MutationObserver API.
Dynamics 365 offers various ways to uniquely identify and display records, which are important for data integrity, performance, and user experience. In this article, we'll explore the differences between Primary Key, Alternate Keys, and Primary Column, along with examples for each.
JavaScript can be employed in Dynamics 365 to enhance the presentation and functionality of columns in entity views. By using a Web Resource and specifying a JavaScript function, you can achieve various types of custom formatting and actions.
Out-of-the-Box (OOB) Command Actions in Microsoft Dynamics 365 offer a range of functionalities designed to facilitate various business processes. In this article, we delve into some of the key OOB Command Actions, providing detailed descriptions, typical usages, and practical examples for each.
Description:
Moves an entity record into a queue.
Usage:
Often used in customer service scenarios for triaging and categorizing incoming cases.
Examples:
Description:
Adds a user to the access team of a specific record.
Usage:
Primarily used for facilitating collaboration on specific records.
Examples:
Description:
Applies a routing rule to an entity record.
Usage:
Typically used in customer service settings to assign cases to specific queues based on attributes like priority, type, or service level.
Examples:
Description:
Calculates the actual value of an entity record, typically used for financial records like Opportunities.
Usage:
Used to re-calculate the actual financial value of an entity based on various criteria.
Examples:
Description:
Changes the status of an Opportunity to "Won" or "Lost."
Usage:
Used in sales pipelines to formally close out opportunities.
Examples:
Description:
Completes a Sales Order, transitioning it to a "Fulfilled" status.
Usage:
Used in order processing and management.
Examples:
Description:
Generates Quote Products based on an existing Opportunity.
Usage:
Used in the sales process to convert opportunities into quotes.
Examples:
Description:
Generates Sales Order Products from an Opportunity.
Usage:
Often used to automate the transition from a closed-won opportunity to the creation of a sales order.
Examples:
Description:
Locks the pricing on an Invoice, making it uneditable.
Usage:
Used for financial compliance and to prevent unauthorized changes.
Examples:
Description:
Locks the pricing on a Sales Order.
Usage:
Used to ensure pricing consistency and compliance after receiving customer approval.
Examples:
Description:
Converts a Lead into an Opportunity, Contact, and/or Account.
Usage:
Used in sales and marketing to move a lead to the next stage of the customer journey.
Examples:
Description:
Removes a user from the access team of a specific record.
Usage:
Used to restrict access to records when necessary.
Examples:
Description:
Closes an Incident (or Case) record as "Resolved."
Usage:
Used in customer service workflows to close cases that have been satisfactorily resolved.
Examples:
Description:
Changes the status of a Quote to "Accepted" or "Declined."
Usage:
Used to formalize the outcome of a quoting process.
Examples:
Description:
Reverts a closed Quote back to an "Active" or editable state.
Usage:
Used to make changes to quotes that have already been closed.
Examples:
Description:
Applies a pre-defined Word template to an entity record to generate a document.
Usage:
Used to automate document creation in various business processes.
Examples:
Understanding and effectively using OOB Command Actions in Dynamics 365 can significantly streamline your business processes. These actions are integral components that can be invoked through workflows, custom code, or Power Automate flows, enabling greater automation and efficiency.