Hide options from OptionSet using JavaScript in Dynamics 365 CRM

January 10, 2023 priyeshwagh777 D365 WebAPI / JavaScript hide options in optionset, hide optionset using javascript, hide optionset values in dynamics 365 crm

Many times, you might not want to show all Options from an OptionSet while it is on a form. So, here’s how you can hide Options from OptionSet using JavaScript in Dynamics 365 CRM!

Scenario

Let’s see the below scenario where these are the options you already see –

You see, there are 3 options for this OptionSet on Contact Form.
Now, you want to hide “Platinum” as an option when a Form loads. So, let’s see how this done.
Now, we can use this information to hide the Option Platinum. We’ll write JS script on the OnLoad of the Contact form.

JS Code

Here’s a JS code sample which will hide the options which you don’t need to display.

Below is the code which you need to register OnLoad of the Contact form and also pass the Context as first parameter –
And when you register it OnLoad, it should look like below –

Code:

oContactCustomization = {
  
    hidePlatinumGrade: function (context) {
        "use strict"; debugger;
        var formContext = context.getFormContext();
        var gradeOptionSet = formContext.getControl("new_grade");
        if (gradeOptionSet !== null) {
            gradeOptionSet.removeOption(3);
        }
    }
};

Here, you get the OptionSet using getControl(); method and then use the variable to then have removeOption(<OptionSet Value>);

Result

Now, when you load the form, you’ll see the option is no longer visible –

Hope this helps!

Here are some Power Automate posts you want to check out –

Thank you!

Asynchronous Merge in Dynamics 365 CRM Power Apps | Power Platform

January 9, 2023 priyeshwagh777 Dynamics 365 CE asynchronous merge, asynchronous merge in dynamics 365 crm, merge records in dynamics 365 crm

If you are familiar with Dynamics 365 CRM and it’s Merge feature for records, here’s a new feature that will let you merge records asynchronously and not hold your time on the screen.

Scenario

Below is how Merging operations would run had Asynchronous Merging not been turned on for your environment –

When you select 2 records, you’ll see the Merge button, of course.
And when you see the preferences which you have to select and move the fields into the Active/Master record.
Once you click OK, you’d see this loading screen as the operation would happen in the background.
Now, depending on how many related/child records you had for the selected records, it would take that longer time to process and it’s inefficient to hold your screen while the merging is happening – much like a Synchronous plugin.
The only advantage is that you would know if anything failed.

Let’s look at how you can enable Asynchronous Merge on your environment and how this will affect your experience along with some pet-peeves.

Enable Asynchronous Merge

Given that you have correct rights for your Power Platform Admin Center [PPAC] (https://admin.powerplatform.microsoft.com/environments), here’s how you can turn the Asynchronous Merge for your environment –

Select the Environment which you want to enable this on –
Expand the Product section and click on Features.
Now, scroll down till you see the option and you’ll see that it is turned off by default.
You can turn this On and Save the Settings.
Once this is turned on, you can see this –
And that’s it, you’ve turned on the Asynchronous Merge for your environment.
Let’s look at how it will behave in the next step.

Please note that this takes about 20-30 minutes to take effect in my experience.

Behavior

Now, let’s select another pair of records to Merge –

I’ve selected the below records to Merge and I can see the Merge button as well.
And you’ll see your usual dialog box to select the fields you want to merge into the master record.
Now, when you click OK, they’ll be merged post they have completed the Parent Check.
To read more about Parent Checking while merging records, you can check this – Parent Check for Merging Records in Dynamics 365 CRM | Power Apps
And the records will be processed in the background for merging and you can continue to work.
Now, in order to find what happened to the merge operation, you can go to Settings > System Jobs.
And look for this operation.
Once you know how to solve the error (see an example in #3 above), the successful Merge operations’ Job start in the background and you’ll see a toast notification on the top right as below
And then, when you look at the System Jobs, you’ll find that the Job has succeeded.

Here’s Microsoft’s Learn document on the same – https://learn.microsoft.com/en-gb/power-platform/admin/async-cascading#merge-record-example?WT.mc_id=DX-MVP-5003911

Hope this helps!

Here are some Power Automate posts you want to check out –

Thank you!

Parent Check for Merging Records in Dynamics 365 CRM | Power Apps

January 8, 2023 priyeshwagh777 Dynamics 365 CE enable parent check in dynamics crm, parent check in crm, parent check merge records, parent checking in merge records in crm

In case you ever tried to Merge records in Dynamics 365 CRM and it failed, you’d usually see the below error –

The error reads – “Unable to merge because sub-entity will be parented differently. You can disable the parent check prior to execution as part of Merge dialog.“

Let’s see why this error occurs and how to solve this.

Scenario

This scenario occurs because the records you are trying to Merge had different Parent records already.
Example –

Notice the below records selected for Merging –
The Contacts to be Merged already belong to different Parent Account
And when you select them for Merging using the Merge button upon their selection.
You’ll also be given Parent Checking selected by Default.
This is what causes the error.
Now, if they either had the same Parent or one of them doesn’t have a parent, this won’t appear and they’ll be Merged.
Now, they’ve been correctly Merged and only 1 record exists.

Hope this helps!

Here are some Power Automate posts you want to check out –

Thank you!

Bulk Delete Cancelling in Dynamics 365 CRM | [Quick Tip]

January 3, 2023 priyeshwagh777 Power Platform Admin Center

In case you want to cleanup some background data in a Sandbox environment but your Bulk Deletion Jobs are failing? Here’s why.

Canceled Bulk Deletion

Below is what you would see –

Once you set a Bulk Deletion job in a Sandbox environment, you notice the below –
The Bulk Deletion Job gets Canceled without even deleting a single record!
There’s a specific reason for why this is happening. Let’s look below.

Background Process

Here’s why the Bulk Deletion job keeps failing –

The reason Bulk Deletion jobs are getting Canceled in the Sandbox environment is because of the Background Processes.
In case the Environment is in Administration Mode.
Open the Environment Power Platform Admin Center (https://admin.powerplatform.microsoft.com/environments) and Go inside the Environment.
Look for the Edit button.
You’ll find that the Administration mode might be enabled. But besides that, the Background operations might be disabled.
This is causing the Bulk Deletion jobs to fail.
And when you restart the process, you’ll find that the Bulk Deletion Jobs will start deleting the items and will be In Progress.

Hope this helps!

Here are some Power Automate posts you want to check out –

Thank you!

Run User Diagnostics in Power Platform Admin Center | Solving User Access Issues for Dynamics CRM

December 29, 2022 priyeshwagh777 Power Platform Admin Center Power Platform Admin Center, run diagnostics in power platform, user access issue in crm, user access issue in dynamics 365 crm, user diagnostics

Many users often reports issue of not being able to access Dynamics 365 CRM even when they’ve been assigned security roles.

So, Power Platform Admin Center will provide you a Diagnostic Tool to quickly check what type of access is missing at the administration level across the below areas –

Sign in blocked for the User at M365 level.
No license for Power Apps / CE Apps.
Not in Security Group of the Dataverse/CRM environment

Let’s see how we can run the Diagnostics and how to solve each of them!

Run Diagnostics on Users

Here’s how you can Run the Diagnostics on the Users in Power Platform Admin Center –

Navigate to the Settings once you select the Environment –
Then, expand the Users + permissions area to see the Users option
Once you see all the Users, you’ll be able to see which Users you want to select and then investigate for diagnostics.
When you click on Run Diagnostics, you’ll see the pan on the right hand side complete some tests and then show the results –
And when you zoom, you’ll see the information as below –
So, when you check the License information in the M365 Portal (considering you have Admin access), you’ll identify that the User is missing the license for Power Apps / Customer Engagement Apps.
When I run this for User whose all levels of access are correct, I’ll see the below –
In other instances, the Sign-in could be blocked as well and this is how it’ll appear. The error message will point out what is causing the User to not access the Dataverse environments.
And when you check the User in the M365 Admin Center, you’ll see that the Sign-in is blocked –
And a final reason that a User is not a part of the Security Group which has been assigned to the Environment itself.
In that case, they’ll see the below error –
So, if you check the Environment in PPAC itself, you can see what Security Group has been applied to the Environment.
And if you look at this Group, you’ll not find the member in the Security Group at the M365 Level.

You can find the complete Microsoft Learn documentation on the same here – https://learn.microsoft.com/en-gb/power-platform/admin/troubleshooting-user-needs-read-write-access-organization#user-diagnostics?WT.mc_id=DX-MVP-5003911

Hope this helps!

Here are some Power Automate posts you want to check out –

Thank you!

Get Data sent to server on Save using Dynamics 365 CRM JavaScript | GetDataXML function

December 27, 2022 priyeshwagh777 D365 WebAPI / JavaScript dynamics 365 crm javascript, getdataxml

Now, in case you are working on forms in Dynamics 365 CRM, and you want to know what all data is changed – There are 2 ways to get this

Scenario

Let’s look at the below scenario where this is useful –

You have a record which you are about to Edit. This is how it looks as of now.
Now, I have an OnSave event on which I’m calling a function to capture what all is being saved.
Now, below is what I want to change and then click Save to save the changes.
And then click Save. Now, I want to capture all this data upon Saving to know and further process what has been changed. Let’s see how we can achieve this using Dynamics 365 CRM JavaScript

getDataXml() method

Here’s how you will see the data to be changed

Below, you see that I’m using formContext.data.entity.getDataXml(); to get the data that was changed and which will be setn to the server to saving/processing.
Please note that here, I’ve used formContext as my variable to store the context passed from the Save event on the form.

Here’s the code for you to copy and change for yourself – var xmlData = formContext.data.entity.getDataXml();
Now, when I run this on the Dev Tools in the Browser, I can see what is being populated when I save the record.
Once I hit debugger, I’ll get the same in the variable I created.
And when I run this variable in the Console to see the complete data, I get this in XML.
And that’s how you can capture data in Dynamics 365 which is being sent to the server for processing/saving.

Hope this helps!

Here are some Power Automate posts you want to check out –

Thank you!

Read OptionSet Labels in Dynamics 365 CRM Plugins | Entity object

December 26, 2022December 26, 2022 priyeshwagh777 Dynamics 365 CRM Plugins Dynamics 365 CRM Plugins, optionset in dynamics 365 crm plugins, optionset labels in dynamics 365 crm, optionset values

Usually, you’d look at the OptionSet in the customiation and decide to write plugin logic based on the code you have noted down.

But, at times, you might want to know what the OptionSet Labels are for these Options, in that case, here’s how you retrieve the labels as well.

In case you are looking to retrieve OptionSet Labels in Power Automate Flow on the Dataverse connector, you can check this post – Read OptionSet Labels from CDS/Dataverse Triggers or Action Steps in a Flow | Power Automate

Scenario

Below is the OptionSet Value and you want to retrieve the Label part when you retrieve or work with RetrieveMultiple or object of the Entity class in Dynamics 365 CRM plugin execution context

OR

And here’s the Data that I’ll be retrieving in my plugin of which I need the label “Silver” instead of the OptionSet value of 1 as seen above.

OptionSet Value

Amongst some methods, I prefer using the below to retrieve the OptionSet Value i.e. the code itself

Lets say I’m looping through a list of records retrieved using RetrieveMultiple in my plugin.
I use entity.GetAttributeValue<OptionSetValue>("field_name").Value; to retrieve the value of the OptionSet option and store it in an Int32 / int variable.
But, this doesn’t give you the Name of the label itself. For that, you’ll need to use a different method. Let’s see below

OptionSet labels using Formatted Values

Below is how you can retrieve Label of the OptionSet value from the Object of the Entity class in Dynamics 365 CRM plugin execution context –

Similar to the above step, I’m retrieving the name of the Label of the same OptionSet value I’m working on from the same example above.
I use entity.FormattedValues["field_name"]; to retrieve the Label of the OptionSet option and store it in a String / string variable.

Here’s where all the other Formatted Values are stored in the RetrieveMultiple’s Object

And that’s how you retrieve the OptionSet Labels in your Dynamics 365 CRM plugin.

Hope this helps!

Here are some Power Automate posts you want to check out –

Thank you!

Microsoft Authenticator app sign-in method types for Microsoft 365 account | Office 365

December 19, 2022 priyeshwagh777 Office 365 Administration MFA enabled Dynamics 365, microsoft 365, microsoft authentication, microsoft authenticator, multi factor authentication, office 365 authentication, office 365 mfa

In case you are setting Authenticator app for accessing your Office 365 account, you have 2 options of authenticating using the Authenticator App from you phone – Notification based and Code based. And see how you can change the preferred method to either of these types!

Notification Based

Here’s how the notification based authentication works –

When you enter your username and password, you’ll see this on your browser intimating that the Approval request has been sent to your phone.
On the phone, you’ll receive the below
And upon opening the notification, the Microsoft Authenticator App will be opened and the permission to Approve or Deny the authentication request for your account will pop-up.
Once you click on Approve, you’ll be able to login.

Code Based

And when Code based method is selected, you’ll see the below –

On the browser when you enter your username and password, you’ll see the below waiting for you to refer to the Authenticator App and enter the same from your phone.
Once you open the Authenticator App and open the Account which you are trying to log in, you’ll see a code in bold letters which refreshes after a time frame.
Once you enter this code, you’ll be able to log in.

Changing the Authentication Method

Here’s how you can change the type of authentication method when you log into your Office 365 –

Navigate to the menu on the top right.
Now, on the left hand side, look for Security Info.
You can then see the different authentication methods you’ve entered like phone, authenticator app etc.
For simplicity, I only have 1 entered i.e. Authenticator App [Microsoft Authenticator].

And now, since Microsoft Authenticator is set as the default method, I’ll also get an option to change the type of authentication set.
I’ll get two options –
“App based authentication – notification” – This will show a pop-up on the phone in the form of a notification which you can choose to Approve or Deny.
“App based authentication or hardware token – code” – This will need you to open the Microsoft Authenticator Apps in your phone and then look for the code in the account and enter it when asked as seen in this post above.
So, you can select the other method apart from the one you have selected and you should be good to go.

Hope this helps!

Here are some Power Automate posts you want to check out –

Thank you!

Adding Editable Grid using the New Power Apps Grid Control in Model-Driven Apps | [Preview]

December 11, 2022 priyeshwagh777 Microsoft PowerApps Dataverse, editable grid, model driven apps, power apps, power apps grid, powerapps

If you are designing your forms in the Model-Driven Apps designer from the Power Apps Maker i.e. https://make.powerapps.com/, here’s how you can add the New Power Apps Grid (which is in Preview at the time of writing this post)

Scenario

For example, you are in Model Driven Apps designer and you are see the existing Grids, they have only 2 areas in Properties –

Select the Grid and you’ll only see 2 areas –
And if you expand them, you won’t find a way to change the control to, for example, Editable Grid.
That’s where the new Power Apps Grid Control comes hand. This is currently in Preview at the time of writing this post.

New Power Apps Grid Control [Preview]

Now, click on the Components section to reveal all the Components that you could add to the Model-Driven Apps form –

You’ll see the More Components section under which you’ll find the new Power Apps Grid Control.
Now, once you drag is on the form where you want it to be, you’ll be asked to select the records it should hold. It’ll ask you to select the Table which you want to display in the sub-grid.
Once you click on Done, make sure the Show Related Records is selected as well and ensure the Table and View selected is correct.
Now, look for Components section and expand the same. Expanding the Components, you’ll be able to select the Editable Grid.
Expand the Components section and you’ll find another button to add more components that are made available.
Now, you’ll be able to select the Editable Grid here.
Now that you have added Editable Grid, click Done.
And once you add, you’ll notice that the Mobile, Web etc will be shown under the new grid. Means this is now set as default and not the other 2 views.
Finally, you can save your changes and publish.
And that’s how you are able to add Editable Grid on the modern Power Apps Model Apps designer using the new Power Apps Grid Component.
And here’s how you’ll be able to add an Editable Grid on the Form using new Power Apps maker.

Here’s the Microsoft Learn link for the same – https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/the-power-apps-grid-control?WT.mc_id=DX-MVP-5003911

Hope this helps!

Here are some Power Automate posts you want to check out –

Thank you!

Filter, Search and Lookup functions in Power Fx | Canvas Apps

November 20, 2022 priyeshwagh777 Microsoft PowerApps canvas apps formula, filter, filter in power fx, lookup, lookup in power fx, search, search in power fx

Here’s how you can use and understand the difference between Filter, Search and Lookup functions if you are new to making Canvas Apps. I’ve tried to explain the usage of these in simple examples!

These functions are part of the Power Fx and are used in Canvas Apps.

Lookup Function – Lookup function in Canvas Power Apps | Power Fx Formula Example
Search Function – Search function in Canvas Power Apps | Power Fx Formula Example
Filter Function – Filter function in Canvas Power Apps | Power Fx Formula Example

Differences between Filter, Search and Lookup

	Filter	Lookup	Search
Results in	Multiple Records	Single Record	Multiple Records
Search Type	Criteria Based	Criteria Based	Text Based

Here’s Microsoft Learn link for detailed criteria & documentation: https://learn.microsoft.com/en-us/power-platform/power-fx/reference/function-filter-lookup#syntax?WT.mc_id=DX-MVP-5003911

Hope this helps!

Here are some Power Automate posts you want to check out –

Thank you!

Scenario

JS Code

Result

Share this:

Like this:

Scenario

Enable Asynchronous Merge

Behavior

Share this:

Like this:

Scenario

Share this:

Like this:

Canceled Bulk Deletion

Background Process

Share this:

Like this:

Run Diagnostics on Users

Share this:

Like this:

Scenario

getDataXml() method

Share this:

Like this:

Scenario

OptionSet Value

OptionSet labels using Formatted Values

Share this:

Like this:

Notification Based

Code Based

Changing the Authentication Method

Share this:

Like this:

Scenario

New Power Apps Grid Control [Preview]

Share this:

Like this:

Differences between Filter, Search and Lookup

Share this:

Like this: