Dynamics 365 CRM Form Switching: A Deep Dive into formSelector and navigate()

In the dynamic landscape of Dynamics 365 Customer Relationship Management (CRM), the ability to present different forms to various user groups based on specific conditions is a common and powerful customization requirement. Fortunately, the formSelector object, coupled with the navigate() function, provides an elegant solution to this challenge, allowing for seamless form switching based on user roles and other criteria.

FormSelector Object

At the heart of this functionality lies the formSelector object, a JavaScript object that acts as a gateway to managing forms within Dynamics 365 CRM. The formSelector object grants access to a collection of items, representing all the forms accessible to the current user. It's important to note that these forms are filtered based on the user's security roles, ensuring a secure and controlled form-switching experience.

Exploring the items Collection

Within the formSelector object, the items collection stands out as a crucial repository of information. Each item in this collection corresponds to a specific form available in the CRM instance. This collection becomes invaluable when checking for user access rights before initiating a form switch.

eg: var formItem = formContext.ui.formSelector.items.get(arg);

In this example, arg represents the identifier or condition used to select a specific form item from the collection.

Navigate() Function

The navigate() function is the key to dynamically switching between forms. Taking a form item as a parameter, this function directs the CRM interface to display the selected form. This proves especially useful when conditions are met, and you want to dynamically present the most relevant form to the user.

eg: formContext.ui.formSelector.items.get(arg).navigate();


Obtain Form Id

Navigate to solution and select the entity and select the form in edit mode. From the URL the id of the form can be obtained.



Check the below code for full implementation.

function formSwitch(executionContext) { // Get the form context var formContext = executionContext.getFormContext(); // Get the value of the field that triggers the change var individualType = formContext.getAttribute("merpin_individualtype").getValue(); // Define the form names to switch between var referralForm = "Your Form Id"; var serviceProvider = "Your Form Id"; // Check the field value and switch forms accordingly if (individualType !== null){ //Referral/Accused if (individualType == 1) { formContext.ui.formSelector.items.get(referralForm).navigate(); } //Service Provider else if (individualType == 2) { formContext.ui.formSelector.items.get(serviceProvider).navigate(); } } }

Form switching happens as soon as JavaScript is provided on the field's OnChange event.





Comments

Post a Comment

Popular posts from this blog

Create HTML table by combining columns from multiple entities

Image
Creating an HTML table in Power Automate is a very commonly used action. Building the HTML table using attributes from a single entity is quite simple and straightforward. However, when it comes to including columns from multiple entities, it requires some extra brainstorming! First, let’s understand how the "Create HTML Table" step works. The "Create HTML Table" step expects an array of objects in the From column. It provides the option to add static table column headers and dynamic table contents. Alternatively, you can let the system handle it automatically. In our case, we are going to create an HTML table by selecting columns from both the Contact and Account entities. From Contact , I will choose the First Name , Last Name , and Email fields, while the Company field will come from the Account entity. Since the "Create HTML Table" step expects an array of objects, we need to create the array with the required fields. To obtain the company name,
Read more

Create and Send Emails with Attachments in D365/Dataverse with Power Automate

Image
  With Power Automate, you can connect to over 300 connectors, including the Outlook connector that can send emails, which is great. However, if you are used to working with Dynamics 365 or Dataverse, one of the key advantages is tracking emails, and if you use the Outlook connector, you cannot do this. This post will show how to create an email, how to add an attachment and how to send an email, so that it’s tracked inside of D365/Dataverse. Create a file or attachment that you want to add onto an email, in my example, I'm going to carry on from my previous post about Word Templates. Then we will "Add a new row" using the Dataverse Connector and the Table name will be Email Message. This will create an email record/row in D365 which requires certain parameters. Firstly, the way email fields to, cc, bcc and from work in D365/Dataverse is via what is called an activity party list. This is a list of rows/GUIDs of rows inside of D365/Dataverse that the email message is conn
Read more