Dynamics 365 Education and Knowledge

How to Remove an Active Unmanaged Layer from the Ribbon in Power Apps (Dynamics 365 CRM) Using ribbondebug=true

noreply@blogger.com (Charles Abi Khirs) — Wed, 06 Aug 2025 19:25:00 +0000

Customizing the ribbon (command bar) in Dynamics 365 CRM via Power Apps can be a powerful way to tailor the user interface to your business needs.

However, during development or testing, and over time, customizations can pile up and it's common that you might have unmanaged customizations.

Therefore, if you're working in an environment with both managed and unmanaged layers, you may run into issues where an active unmanaged layer causes unexpected behavior or UI inconsistencies.

One of the most frustrating issues is when a ribbon behaves incorrectly due to an active unmanaged layer, often created outside of a solution.

Fortunately, there’s a powerful tool to inspect and resolve this: the ribbondebug=true URL parameter.

In this post, we'll walk through how to identify and remove an active unmanaged layer from the ribbon in Power Apps for a model-driven Dynamics 365 CRM app using the ribbondebug=true diagnostic tool.

🔍 What Is an Unmanaged Layer?

In the context of Power Platform, customizations are stored in layers:

Managed layers come from imported managed solutions.
Unmanaged layers are changes made directly in an environment, typically during development.

Unmanaged layers take precedence over managed ones. If an unmanaged layer exists, it will override the behavior of any managed customizations underneath it. This is especially true for ribbon (command bar) customizations.

🎯 Why Remove the Unmanaged Layer?

You might want to remove an unmanaged layer when:

You accidentally made changes outside your managed solution.
The ribbon behaves differently than expected in higher environments.
You want to ensure consistency across environments by eliminating ad-hoc UI changes.

🧠 What Is `ribbondebug=true`?

Appending &ribbondebug=true to your Dynamics 365 URL enables the Command Checker Ribbon debugger, which provides insights into:

Command definitions.
Custom actions.
JavaScript functions.
Button locations and behaviors.
And more importantly — unmanaged layers!

⚠️ When to Use This

Use this technique when:

You're unsure where a ribbon customization is coming from.
The Power Apps UI doesn’t show all ribbon commands.
You suspect an unmanaged layer is overriding managed behavior.

🛠️ Steps to Identify and Remove an Unmanaged Ribbon Layer

Step 1: Open Your Model-Driven App with Debug Mode Enabled

Log into https://make.powerapps.com.
Open your model-driven app.

In the address bar, append the following to the URL:

https://yourorg.crm.dynamics.com/main.aspx?appid=XXXXXX&ribbondebug=true

Press Enter to reload the app in ribbon debug mode.

Step 2: Inspect the Ribbon

Once in debug mode, click on the ... of the ribbon and scroll down until you reach the Command Checker. You’ll see extra debug details like:

Button IDs.
Command names.
Enable rules and display rules.
Ribbon source file.

Step 3: Command Checker pane

The command checker pane will open and display all the buttons available for the entity.
Search for your specific ribbon button and click on it.
The button properties with its command will be displayed within the command checker pane.

Step 4: Check the Unmanaged Layer

In the Button or Command Properties tab, click on View button solution layers or View command solution layer link.
You will have this option on all the elements that could have unmanaged layer.
Once you click on the link, you will be able to see the layers of this corresponding button element.

Step 5: Remove the Unmanaged Layer

In case the ribbon button property contains an unmanaged layer, it will be displayed.
Click Remove active component layer link to delete the unmanaged layer.
Confirm the removal to revert the ribbon to its managed version — effectively "cleaning up" customizations.

Step 6: Regenerate ribbon metadata

Once the unmanaged layer is removed, it will disappear.
Now, you have to click Regenerate ribbon metadata button.
This action will take around 15 minutes to finish.
Reload the app with and without ribbondebug=true to confirm everything behaves correctly.

💡 Best Practices

Always work in solutions, not directly in the default layer.
Keep unmanaged changes only in development environments.
Regularly export and back up your solutions.
Use source control or ALM (Application Lifecycle Management) tools when possible.

🧪 Example Use Case

Imagine you deployed a managed solution that hides a "Delete" button for a custom entity. But in your test environment, the "Delete" button still appears.
By using ribbondebug=true, you discover there's an unmanaged display rule that's overriding your managed rule. Removing the unmanaged layer resolves the issue immediately.

✅ Summary

The ribbondebug=true flag is a powerful (and underused) tool to diagnose and clean up ribbon issues in Dynamics 365 CRM. Use it to expose and identify unmanaged layers that affect the ribbon and then remove them.
Removing an active unmanaged layer from the ribbon in Power Apps is an important step for maintaining clean and predictable UI customizations across environments.

Hope This Helps!

DYNAMICS 365 CRM ADDING ENTITY METADATA AFTER ADDING THE TABLE TO A SOLUTION

noreply@blogger.com (Charles Abi Khirs) — Wed, 16 Jul 2025 17:06:00 +0000

In Microsoft Dynamics 365 CRM, solutions function as the fundamental units for packaging, deploying, and managing system customizations across environments.

By default, when a table is added to a solution, only a subset of its components is included.

This can lead to deployment failures or functional discrepancies if dependent components (such as views, forms, or metadata) are omitted.

To ensure consistency and completeness during solution transport, it's often necessary to explicitly include additional components within the solution.

One such critical component is the table’s metadata, which governs schema-level definitions and behaviors essential for proper execution in target environments.

This article covers how to manually add only the entity metadata after including the table in a solution:

🧠 Key insights into metadata and why it matters:

🧱 Table Segmentation:
In Dynamics 365, you can segment tables by including specific components or metadata when adding them to a solution.
🔍 Including Metadata:
When segmenting a table, you have the option to include "table metadata" that encompasses properties like auditing, duplicate detection, change tracking etc... without including the table's individual components like columns, views, forms, or other components.
💡 Why Include Metadata?
This is useful when you need to apply changes to the table's core settings or behaviors without needing to include all the table's components in the solution.
For example, if you enabled auditing or change tracking in your development environment and want these changes to be deployed to another environment, you must include the table metadata.
🧩 Including metadata ensures:
- Consistency across environments.
- Completeness of the table’s configuration.
- Avoidance of manual rework or patching missing components post-deployment.
By explicitly including entity metadata after adding the table, you avoid pitfalls and ensure that your solution behaves reliably across environments.
🎯 All or Nothing:
Currently, it's an "all or nothing" approach when including metadata; you can't selectively choose which metadata to include. However, Microsoft says they are aware of the need for selective metadata inclusion.

✅ If you've already added a table and forgotten to include metadata, here are the steps to do it without removing the entity from the solution:

Using Classic Interface:
- Go to Settings > Solutions and open your existing solution.
- Click Add Existing > Entity to verify if the table is already added.
- Open the Solution and locate the table already included.
- Click on the table name to open its configuration screen within the solution.
- Once inside the table's configuration window, click "Add Subcomponents" button.
- In the Add components pop-up, you’ll see tabs for Forms, Views, Fields etc. To specifically include the metadata, tick the "Include entity metadata" checkbox.
- Click Finish after including the necessary metadata.
- Back in the solution window, Publish All Customizations to ensure changes take effect.
Using Power Apps Maker Portal
- Open the Power Apps Maker Portal and select the appropriate Environment.
- Go to Solutions, and open your existing solution.
- Click Add Existing > Table to verify if the table is already added.
- Locate the table already included.
- Click on the table name to open its settings screen within the solution.
- From the ribbon, click Advanced > Table Segmentation Properties.
- In the Table Segmentation Properties pane, tick the "Include table metadata" checkbox.
- Click Save and publish customizations to ensure changes take effect.

Hope This Helps!

DYNAMICS 365 CRM HOW TO CHECK THE IMPORT SOLUTION PROGRESS

noreply@blogger.com (Charles Abi Khirs) — Mon, 07 Jul 2025 17:52:00 +0000

Importing solutions to the DEV, TEST, UAT or PROD environments in Dynamics 365 CRM is a common activity for system administrators and developers.

However, when importing large or complex solutions, it can be frustrating to sit and wonder: How far along is the import? or Is it stuck?

Luckily, with the right tools, you can track the progress of a solution import job with actual percentages — giving you more visibility and control over your deployment processes.

In this post, we’ll explore the steps needed to see the solution import progress:

Step 1: Open Dynamics CRM Advanced Find, where the solution is being imported.
Step 2: In Look for: Select Import Jobs entity and give the condition Created On = Today to narrow down the result.
Step 3: Make sure that the column Progress is added to the view.
Step 4: Identify your Solution Name and check the Progress (%) column in percentage.
Step 5: Once the import is done, you can verify that the progress is now 100.

Bonus Tips:

You can use the Solution Transfer Tool in XrmToolBox to help tracking the progress of solution imports.
You can use Web API calls, to monitor the import status by querying the importjob table in Dataverse.
You can query it directly using Web API tools or Power Automate. [EnvironmentURL]/api/data/v9.2/importjobs?$select=progress,statuscode,name

Hope This Helps!

HOW TO GET MICROSOFT DYNAMICS 365 FORM TYPE IN JAVASCRIPT

noreply@blogger.com (Charles Abi Khirs) — Thu, 11 Apr 2024 21:10:00 +0000

When working with forms, you have the ability to create different types of forms based on your needs : Main Form, Quick View Form, Quick Create Form, or Card Form.

The most common type is the Main Form which is the form where most of time the users work. The main form itself has different status that represents specific functionality or use, this is known as well as form type .

The purpose of this post is to know what are the different types of the Main form and how to get it using JavaScript, so you will have the ability to change its behavior based on its type that will be reflected for end users.

Getting the type of form can be done in JavaScript using the function formContext.ui.getFormType().

The following JavaScript function will display a popup message with the form type:

function getFormType(context) {
var formContext = context.getFormContext();
var formType = formContext.ui.getFormType();
var messageToDisplay = "";
switch (formType) {
case 1:
messageToDisplay = "Create / Quick Create form";
break;
case 2:
messageToDisplay = "Update form";
break;
case 3:
messageToDisplay = "Read Only form";
break;
case 4:
messageToDisplay = "Disabled form";
break;
case 6:
messageToDisplay = "Bulk Edit form";
break;
default:
messageToDisplay = "Undefined form";
}
var alertMessage = { text: messageToDisplay };
Xrm.Navigation.openAlertDialog(alertMessage, null);
}

The below table lists the different Dynamics 365 form types and their respective JavaScript return values:
Type: Number
Description: Form type. Returns one of the following values

Values		Form type
0		Undefined
1		Create / Quick Create
2		Update
3		Read Only
4		Disabled
6		Bulk Edit

Hope This Helps!

DISABLE ALL FORM FIELDS IN DYNAMICS 365 USING JAVASCRIPT

noreply@blogger.com (Charles Abi Khirs) — Fri, 29 Dec 2023 13:56:00 +0000

To make the form read-only in Dynamics 365 you have 3 options: changing record status to Inactive, Business rule, JavaScript.

The purpose of this article is to know how to make all form fields disabled with JavaScript.

Changing record status to Inactive might not very suitable for some cases where cascading rules might be applied to children records.

On the other hand, even though it is a low code solution, using business rule to make all fields read-only will be very time consuming especially if a field is removed from the form or a new field is added to the form.

However, using JavaScript will allow you to set all form fields to read-only dynamically with a small piece of code and you can do it based on a certain condition of an attribute value.

Make read-only the whole fields of a form based on a certain condition
The below function can be called on the event you need and will loop through all the fields to make them read-only

// Disable all form fields
function disableAllFormFields(context) {
var formContext = context.getFormContext();
formContext.ui.controls.forEach(function (control, i) {
if (control && control.getDisabled && !control.getDisabled()) {
control.setDisabled(true);
}
});
}

Hope This Helps!

CHANGE ROLLUP FIELD RECURRENCE SCHEDULE IN DATAVERSE / DYNAMICS 365

noreply@blogger.com (Charles Abi Khirs) — Wed, 06 Dec 2023 21:03:00 +0000

One of the features in Dynamics 365 is the rollup field type where you can perform aggregation and calculation of data in a parent record based on child records.

You create a rollup field by adding a new field, choosing the field and data type, and building the logic for the calculation.

One of the important consideration of a rollup field is the frequency of its calculation where, for each entity that contains a rollup field, a recurring system job will be automatically created in order to calculate the rollup field. This calculation is done asynchronously based on a frequency set.

By default, it is set to 1 hour, however, you can change this frequency by following the below steps.

In the environment, go to Settings page and under Audit and logs menu, click on System jobs
Choose the view All Rollup Fields Calculation Jobs and open the calculate rollup fields job which contains the entity name. For this article, the entity is account.
Open the Job and click on Actions -> Modify Recurrence
In the Modify Recurrence page, adjust the frequency as per needed and click OK

On the other hand, you might have scenarios where you need that the calculation to be done immediately, therefore, you can force the calculation of a rollup field using JavaScript or C# as per this article

Hope This Helps!

OPEN DYNAMICS 365 ADVANCED FIND BY DEFAULT IN DETAILED MODE

noreply@blogger.com (Charles Abi Khirs) — Wed, 25 Oct 2023 20:46:00 +0000

To the ones who use Advanced Find, today's article is related to how you can optimize its usage.

By default, and when you open the Advanced Find page, it will display the current view you are seeing, with the conditions predefined.
For example Active accounts or Active contacts will display the condition Status | Equals | Active.

In addition, you will notice that you will not be able to apply more filters in the Advanced Find, unless you click the Details button.

In this article, we will see how to open the Advanced Find in detailed mode and directly change the filters without clicking additional button

Advanced Find is by default opened in Simple mode
Once you click Details button, you can change the existing filters and add new ones if needed
Changing default mode of the Advanced Find
The user can change the default mode of the Advanced Find by going to his personal options under Personalizations Settings menu
In the Personal Options page, under the General tab, set the Select the default mode in Advanced find to Detailed instead of Simple
Advanced Find opened in Detailed mode. Once the setting is changed, the Advanced Find will open in Detailed mode where the user can directly change or apply more filters

Hope This Helps!

SEARCH BY GUID IN DYNAMICS 365

noreply@blogger.com (Charles Abi Khirs) — Wed, 20 Sep 2023 19:59:00 +0000

Is it possible to search for a CRM record using its GUID ?

Well, NO it is not possible and YES it is possible!!!

As always has been, it is not possible to search for a record by its guid in Advanced Find and in the Quick view search.

However, in the model-driven app Edit filters functionality, it is possible to search for a record by its Guid.

How it works, let's check the 3 different places where we can search for a records.

Advanced Find search
Using the Advanced find feature, you cannot put a GUID value to search for. You will directly receive an error notification eventhough when you download the fetchXml, the Guid of the record will be there.
Quick view search
Using the search box on top of the view, you can enter a GUID value, but you will not have any data in the result since it will search for the guid value within the columns selected in the quick find view.
Edit the view with advanced filter queries
Using this functionality, you can search by GUID for a record and it will be automatically reflected in the search criteria if the record with the specified GUID exists in the table.

Hope This Helps!

SAVE FORM IN DYNAMICS 365 JAVASCRIPT

noreply@blogger.com (Charles Abi Khirs) — Tue, 22 Aug 2023 20:31:00 +0000

In Dynamics 365, you may need to save a CRM form automatically in JavaScript upon a specific action on the form.

In order to do that, the function formContext.data.save(saveOptions).then(successCallback, errorCallback); can be used to save the record asynchronously with callback functions to be executed after the save operation is completed.

The following example will display a successful message if the save operation is completed, and a failure message if not.

formContext.data.save(1).then(
function () {
alert("Successfully Saved!");
},
function () {
alert("Failed while saving!");
});
The save function takes saveOptions as a parameter to specify options for saving the record and has the following properties:
- saveMode: (Optional) Specify a value indicating how the save event was initiated. Noting that setting the saveMode does not actually take the corresponding action;
For a list of supported values, see the return value of the getSaveMode method as per following link
For a full list of the properties, check the following link
successCallback: This function will be called when the operation succeeds.
errorCallback: This function will be called when the operation fails and the following properties will be passed:
- errorCode: The error code
- message: A localized error message

Previously, we were able to synchronously save the record using the following script formContext.data.entity.save(saveOption); with the option to close the form or open a new form after the save is completed.
However, this method is now deprecated and it is not recommended to use it anymore.

If no parameter for the save options is passed, the record will simply be saved. This is the same of using the Save command.
saveandclose: This is the same of using the Save and Close command formContext.data.entity.save("saveandclose");
saveandnew: This is the same of using the Save and New command, a new form will be after the save is completed formContext.data.entity.save("saveandnew");

Hope This Helps!

CHANGE CONTROL LABEL DURING RUNTIME IN DYNAMICS 365 USING JAVASCRIPT

noreply@blogger.com (Charles Abi Khirs) — Fri, 26 May 2023 20:31:00 +0000

In Dynamics 365, we might have to change CRM control label at runtime for specific needs.

This can be easily done through JavaScript code by calling the function setLabel() that sets the label of the control.

One function, several ways you can use to change the label based on the control type.

Dynamically change a tab label
Using the function setLabel, you can change a tab label during runtime as per the below code snippet.

var runtimeTabLabel = "Runtime Tab Label";
formContext.ui.tabs.get("<tabName>").setLabel(runtimeTabLabel);
Dynamically change section label
Using the function setLabel, you can change a section label during runtime as per the below code snippet.

var runtimeSectionLabel = "Runtime Section Label";
formContext.ui.tabs.get("<tabName>").sections.get("<sectionName>").setLabel(runtimeSectionLabel);
Dynamically change field label
Using the function setLabel, you can change a field label during runtime as per the below code snippet.

var runtimeFieldLabel = "Runtime Field Label";
formContext.getControl("<fieldName>").setLabel(runtimeFieldLabel);
Dynamically change subgrid label
Using the function setLabel, you can change a subgrid label during runtime as per the below code snippet.

var runtimeSubgridLabel = "Runtime Subgrid Label";
formContext.getControl("<subgridName>").setLabel(runtimeSubgridLabel);
On the other hand, you can use the function getLabel() to return the label for the control

Hope This Helps!

CHECKING DIRTY FIELDS IN DYNAMICS 365 USING JAVASCRIPT

noreply@blogger.com (Charles Abi Khirs) — Tue, 21 Mar 2023 22:17:00 +0000

In Dynamics 365, there is a common need to identify which fields have been modified on the form during an update.

One way is by creating a Plugin that will receive data of the modified fields in the current update event.

However, the purpose of this article is to check how to identify the modified fields through JavaScript.

It is done by verifying if the form or fields are in a dirty state which indicates if they have been changed.

Three methods are available that you can use to get if the form or specific fields are dirty.

Check if form is dirty to verify if any field on the form has been changed.
Using the function getIsDirty, you can check if any field on the form has been modified.
formContext.data.entity.getIsDirty();
This function will return true if the form is dirty, false otherwise.
Check if a field is dirty to verify if a specific field on the form has been changed.
formContext.getAttribute("schema-field-name").getIsDirty();
This function will return true if the field is dirty, false otherwise.
Display all the modified fields to verify what fields on the form have been changed.
formContext.data.entity.getDataXml();
This function will get the list of attributes that have been modified on the form with the values of each field.

A Xml result having a parent tag and inner elements where the root tag contains the entity logical name and the inner tags contain the fields' logical name with the current value of each field.

Hope This Helps!

SET DYNAMICS 365 MULTISELECT OPTIONSET FIELD IN C#

noreply@blogger.com (Charles Abi Khirs) — Sun, 19 Feb 2023 17:05:00 +0000

As known, Multi-Select Option set field helps you select more than one option.

Sometimes, you want to dynamically select one or more option in the multiselect field.

In another post, we saw how to set a value of a multiselect option set field in JavaScript

In this post, we will see how to set options of a multiselect option set field in C#

The below code snippet can be used to add the needed options you want to set for the multi select option set field
OptionSetValueCollection osvc = new OptionSetValueCollection();
osvc.Add(new OptionSetValue(<integerValueOptionSet>));
Once the needed options are added to the OptionSetValueCollection, you can add it to the list of attributes of the entity record

Hope This Helps!

SETSUBMITMODE IN DYNAMICS 365 JAVASCRIPT

noreply@blogger.com (Charles Abi Khirs) — Sun, 15 Jan 2023 13:05:00 +0000

In Dynamics 365, there are some scenarios where you want to always submit or never submit the value of a column into the database.

To do this, you have to use the JavaScript method setSubmitMode that will control whether the data for a column is submitted when a record is created or saved.

In case you have a column that you are not interest to capture its data, use the never parameter for the setSubmitMode method.

While, if you want to force a column value to be submitted whether it has changed or not, use the always parameter for the setSubmitMode method.

Use one of the below three options for the setSubmitMode function as per the below.

always: The data is always sent with a create/save event and can be captured within the entity attributes in a plugin
function setSubmitModeField(context) {
var formContext = context.getFormContext();
formContext.getAttribute("primarycontactid").setSubmitMode("always");
}

Column's data always captured in the plugin: throw new Exception(account.Contains(Account.Fields.PrimaryContactId).ToString());
never: The data is never sent with a create/save event and cannot be captured within the entity attributes in a plugin
For example, if the column is modified and after saving the form, the column's value will be replaced with the old value and will not be submitted.
function setSubmitModeField(context) {
var formContext = context.getFormContext();
formContext.getAttribute("primarycontactid").setSubmitMode("never");
}

Column's data never captured in the plugin: throw new Exception(account.Contains(Account.Fields.PrimaryContactId).ToString());
dirty: This is the default behavior where the data is submitted with the create/save event when the value of the column has changed
function setSubmitModeField(context) {
var formContext = context.getFormContext();
formContext.getAttribute("primarycontactid").setSubmitMode("dirty");
}
On the other hand, use the function getSubmitMode to return the option indicating when data from the column will be submitted when the record is created/saved

Hope This Helps!

ACCESS FIELDS OF QUICK VIEW FORM THROUGH JAVASCRIPT IN DYNAMICS 365

noreply@blogger.com (Charles Abi Khirs) — Fri, 06 Jan 2023 19:52:00 +0000

As known, quick view controls are associated to lookup fields that are included in a form and they are added to display specific information about the selected record in the lookup field.
This will increase user experience where the users do not need to navigate to a different record to see the information needed.

However, you might have requirements where you want to check a field value of the quick view form control in order to apply specific behavior on the main form.

In this post, we will see how to access Quick View Form fields through JavaScript in Dynamics 365.

For the sake of this post, we will work with a contact quick view form control on the account form.

Based on the primary contact Relationship Type field, a specific section on the account form will be displayed.

Relationship Type field of the contact = Employee => Employee section on the account form will be displayed
Relationship Type field of the contact = Partner => Partner section on the account form will be displayed
Relationship Type field of the contact = Client => Client section on the account form will be displayed
Finally, the following JavaScript function can be used to manage the access of the Quick Find form fields and called on the account’s form onload and primary contact field onchange events

function showHideSectionsBasedOnQuickViewField(context) {
var formContext = context.getFormContext();
var contactQuickViewControl = formContext.ui.quickForms.get("account_contact_quickview");
if (contactQuickViewControl !== undefined) {
if (contactQuickViewControl.isLoaded()) {
var relationshipType = contactQuickViewControl.getControl("customertypecode").getAttribute().getValue();
switch (relationshipType) {
case 1: // Employee
formContext.ui.tabs.get("SUMMARY_TAB").sections.get("SUMMARY_TAB_section_employee").setVisible(true);
formContext.ui.tabs.get("SUMMARY_TAB").sections.get("SUMMARY_TAB_section_partner").setVisible(false);
formContext.ui.tabs.get("SUMMARY_TAB").sections.get("SUMMARY_TAB_section_client").setVisible(false);
break;
case 2: // Partner
formContext.ui.tabs.get("SUMMARY_TAB").sections.get("SUMMARY_TAB_section_employee").setVisible(false);
formContext.ui.tabs.get("SUMMARY_TAB").sections.get("SUMMARY_TAB_section_partner").setVisible(true);
formContext.ui.tabs.get("SUMMARY_TAB").sections.get("SUMMARY_TAB_section_client").setVisible(false);
break;
case 3: // Client
formContext.ui.tabs.get("SUMMARY_TAB").sections.get("SUMMARY_TAB_section_employee").setVisible(false);
formContext.ui.tabs.get("SUMMARY_TAB").sections.get("SUMMARY_TAB_section_partner").setVisible(false);
formContext.ui.tabs.get("SUMMARY_TAB").sections.get("SUMMARY_TAB_section_client").setVisible(true);
break;
default:
formContext.ui.tabs.get("SUMMARY_TAB").sections.get("SUMMARY_TAB_section_employee").setVisible(false);
formContext.ui.tabs.get("SUMMARY_TAB").sections.get("SUMMARY_TAB_section_partner").setVisible(false);
formContext.ui.tabs.get("SUMMARY_TAB").sections.get("SUMMARY_TAB_section_client").setVisible(false);
}
}
else {
setTimeout(showHideSectionsBasedOnQuickViewField, 10, context);
}
}
}

Hope This Helps!

FILTER LOOKUP IN DYNAMICS 365 BASED ON CONDITION IN JAVASCRIPT WITH ADDCUSTOMFILTER AND ADDPRESEARCH

noreply@blogger.com (Charles Abi Khirs) — Sun, 06 Nov 2022 17:08:00 +0000

Working with lookups provide you many possibilities regarding filtering the records displayed in the lookup.

You can do it by using the out of the box related records filtering in the lookup field properties, however and in some scenarios, this approach does not provide what you need.

Therefore, writing JavaScript code is mandatory to achieve what you want, which is the topic of this post

In other post, we saw how to filter lookup field in JavaScript using the function addCustomView

In this post, we will see **how to filter a lookup field in JavaScript using addPreSearch and addCustomFilter functions**.

For the sake of this post, we will filter the Parent Account lookup in the account form based on the category field

We have to create a fetch Xml, where we are going to use the filter part only and not the whole fetch Xml
In our example, we will use the account category as the condition to filter the list of available accounts in the parent account lookup
Call the below function on form load and use the addPreSearch that takes a function as a parameter where the filter is done using addCustomFilter

function applyParentAccountPreSearch(context) {
var formContext = context.getFormContext();
formContext.getControl("parentaccountid").addPreSearch(applyParentAccountFilter);
}
Below is the function where the addCustomFilter is used to filter the lookup based on the condition you set

function applyParentAccountFilter(context) {
var formContext = context.getFormContext();
var filter = '<filter type="and">';
filter += '<condition attribute="accountcategorycode" operator="eq" value="2" />';
filter += '</filter>';
formContext.getControl("parentaccountid").addCustomFilter(filter);
}
You can now go to an account record and click to select a record from the Parent Account lookup, you will notice that the accounts are now filtered based on the condition you have added
In the above example, we put the condition as a static value but of course you can do it to be dynamically set based on your needs
Another optional parameter can be passed to the addCustomFilter function which the entity that the view will look up to
The new filter will be added to the default filter already applied of the lookup view with the AND operator
In case you didn't use the filter element, you will get the following error "Invalid Child Node, valid nodes are filter, order, link-entity, attribute, all-attributes, no-attrs"

Hope This Helps!

DISABLE SECURITY DEFAULTS FOR DYNAMICS 365 ENVIRONMENT

noreply@blogger.com (Charles Abi Khirs) — Sun, 11 Sep 2022 21:09:00 +0000

When creating a Dynamics 365 Trial environment, each time you want to login, you will be promted by a security message.

Security Defaults are a series of settings enabled by default on your Microsoft Office 365 account, to provide better security where every user is required to log in using Multi-Factor Authentication (MFA).

To know more information about the Security Defaults, check Microsoft's documentation.

In this post, we will see how to disable Security Defaults message when logging in.

You can change the security defaults from Office 365 Admin center or from the Azure Portal

Log into your Office 365 management area > Admin > Azure Active Directory or from the Azure portal > Azure Active Directory
Under Azure Active Directory, click Properties and then Manage Security Defaults
In the right pane, select No for Enable security defaults, and click Save
A Success message will appear indicating that Security Defaults changes have been saved
Click Save again to publish the changes on the tenant
Once done, you will no longer be prompted to set up Security Defaults when logging in

Hope This Helps!

GET THE SIZE OF DYNAMICS 365 TABLES FOR ON PREMISES ORGANIZATION

noreply@blogger.com (Charles Abi Khirs) — Sun, 04 Sep 2022 18:58:00 +0000

In previous post, we saw how to get the size of Dynamics 365 / Dataverse tables for an online environment

In this post, we will see how to get the size of Dynamics 365 tables for an on premises organization.

In order to check the tables size, you need to open the SQL server Management Studio and execute the below query

In the Management Studio, click New Query or expand the Databases list and right click the needed database > New Query
In the query editor, execute the below query by putting the correct database name

USE <DatabaseName>
GO

SELECT
t.Name AS TableName,
s.Name AS SchemaName,
p.Rows AS RowCounts,
SUM(a.total_pages) * 8 AS TotalSpaceKB,
SUM(a.used_pages) * 8 AS UsedSpaceKB,
(SUM(a.total_pages) - SUM(a.used_pages)) * 8 AS UnusedSpaceKB
FROM
sys.tables t
INNER JOIN sys.indexes i ON t.object_id = i.object_id
INNER JOIN sys.partitions p ON i.object_id = p.object_id AND i.index_id = p.index_id
INNER JOIN sys.allocation_units a ON p.partition_id = a.container_id
LEFT OUTER JOIN sys.schemas s ON t.schema_id = s.schema_id
WHERE t.Name NOT LIKE 'dt%'
AND t.is_ms_shipped = 0
AND i.object_id > 255
GROUP BY t.Name, s.Name, p.Rows
ORDER BY SUM(a.used_pages) * 8 DESC;
GO
Once the query is executed, you will get the list of tables sorted by its used space
This query can give you insights in case you are facing some performance issues in your environment where it might be related to the tables size

Hope This Helps!

GET THE SIZE OF TABLES IN DYNAMICS 365 / DATAVERSE ENVIRONMENT

noreply@blogger.com (Charles Abi Khirs) — Sun, 28 Aug 2022 18:22:00 +0000

Data size is continuously growing over the time. Thus, data storage and usage with the increasing complexity and new supported data types, is becoming an essential tool for the organizations to be able to expand their business.

Therefore, knowing the data volume becomes very critical and in Dataverse, you are able to check the space reserved by each table.

In this post, we will see how to get the size of Dynamics 365 / Dataverse tables for an environment.

Using the Capacity page in the Power Platform Admin Center, you can get the size of each table (in MB).

Login to Power Platform admin Center
Under the Resources menu, click the Capacity option
Select the Dataverse tab, or click on the Trial tab to check the environments
Click the Details (graph) button for the specific environment to open a detailed report of Usages for Database Usage, File Usage, and Log Usage
To check the size of each table, from the Top database capacity use, by table section, click the burger menu > Download all tables option
A CSV file will be downloaded where you can check the size for each table sorted by the highest space usage in MB
This report can give you some insights in case you are facing some performance issues in your environment where it might be related to the tables size

Hope This Helps!

SELECT ALL OPTIONS OF MULTISELECT OPTION SET (CHOICES) FIELD IN DYNAMICS 365

noreply@blogger.com (Charles Abi Khirs) — Mon, 22 Aug 2022 05:02:00 +0000

Multiselect or Choices field type has some limitations when working with them. One of these limitations is to select all the options by default.

Since the multiselect fields cannot be used in business rules, therefore, you have to go with JavaScript to achieve this need.

For this post, we will see how to select all options of a Multiselect / Choices field in Dynamics 365.

The below code snippet will get all the available options in the multiselect field and will select them all
// Select all the options in the multiselection field on create form
function setMultiselectDefaultValues(context) {
var formContext = context.getFormContext();
if (formContext.ui.getFormType() === 1) {
var options = formContext.getAttribute("cak_multiselectoptionfieldcode").getOptions(); // Get all the available options
var selectOptions = [];
for (var i = 0; i < options.length; i++) {
selectOptions.push(options[i].value); // Add the options into an array
}
formContext.getAttribute("cak_multiselectoptionfieldcode").setValue(selectOptions);
}
}
Create your JavaScript web resource and add it to the needed solution
From the form onLoad event, call the specific function

Hope This Helps!

DATA CENTER REGIONS FOR DYNAMICS 365

noreply@blogger.com (Charles Abi Khirs) — Wed, 20 Jul 2022 14:48:00 +0000

The online version of Dynamics 365 is being hosted in datacenters that exist in many regions.
Based on the country/region you selected during the sign-up, the datacenter will be chosen to store data for your environments.

This selection will be reflected into the URL of your Dynamics 365 environment where you can guess the region from it.

In this post, we will see the latest list of datacenter regions for Dynamics 365 Online with the URL for each region.

Here is the list of the latest of Dynamics 365 Online data center regions

#	Region	URL
1	North America (NAM)	crm.dynamics.com
2	United States Government Community Cloud (US GCC) High	crm.microsoftdynamics.us
3	Microsoft Cloud Germany (DEU)	crm.microsoftdynamics.de
4	China (CHN)	crm.dynamics.cn
5	South America (LATAM/ SAM)	crm2.dynamics.com
6	Canada (CAN)	crm3.dynamics.com
7	Europe, Middle East, Africa (EMEA / EUR)	crm4.dynamics.com
8	Asia Pacific (APAC/ APJ)	crm5.dynamics.com
9	Australia (OCE)	crm6.dynamics.com
10	Japan (JPN)	crm7.dynamics.com
11	India (IND)	crm8.dynamics.com
12	North America 2 (US Gov GCC)	crm9.dynamics.com
13	United Kingdom (UK/ GBR)	crm11.dynamics.com
14	France (FRA)	crm12.dynamics.com
15	South Africa (ZAF)	crm14.dynamics.com
16	United Arab Emirates (UAE)	crm15.dynamics.com
17	Germany (GER)	crm16.dynamics.com
18	Switzerland (CHE)	crm17.dynamics.com
19	Norway (NOR)	crm19.dynamics.com
20	Singapore (SGP)	crm20.dynamics.com
21	Korea (KOR)	crm21.dynamics.com

Hope This Helps!

CHANGE USER BUSINESS UNIT WITHOUT REMOVING SECURITY ROLES IN DYNAMICS 365

noreply@blogger.com (Charles Abi Khirs) — Sun, 10 Jul 2022 17:18:00 +0000

Since the first versions of the Dynamics 365 product, the business units, users, and security roles are directly linked together and form the base of the security model in the system, where every user must belong to one business unit and must have one or more security roles assigned to him.

As you know, security roles are specific to each business unit, where a version of the security role of the root business unit will be replicated and inherited for every business unit in the hierarchy.

In addition, changing a user business unit will remove all the security roles assigned to the user from the previous business unit, and you need to reassign them manually for the new business unit.

Starting 2021 Release Wave 2 Updates, this behavior can be overridden and we can change the user business unit without removing the assigned security roles.

In this post, we will see how to change user business unit without manually re-assigning the security roles in Dynamics 365.

In order to keep the security roles of the user when changing his business unit, a new setting has been added that give you the ability to enable it and to keep the security roles after the change of business unit

Import the solution Organization Settings Editor after installing it
After the solution is successfully imported, open its configuration page
Scroll down to the option DoNotRemoveRolesOnChangeBusinessUnit
Click Add to enable it in the system
The default value is set to false
Click Edit to change the value to true
Now in the user page, change the business unit and check the security roles
As expected after updating the setting to true, the same security roles are still assigned but are the ones under the new business unit
The setting DoNotRemoveRolesOnChangeBusinessUnit is still not available for the Dynamics 365 on-premises (checked on version 9.1.2.2)

Hope This Helps!

CREATE APPICATION USER FOR DYNAMICS 365

noreply@blogger.com (Charles Abi Khirs) — Mon, 04 Jul 2022 17:55:00 +0000

In Dynamics 365, you can create an unlicensed user in your environment, it is called Application user.

This type of user will have access to the data of your environment on behalf of the user who is using your application.

However, each Azure Active Directory registered application, you can only create one application user.

Previously, we were able to create this type of users from the Users area under the Settings > Security menu. Currently, it is done through the Power Platform Admin center

In this post, we will see how to Create an Application User for Dynamics 365.

Below are the instructions to create an application user

Log on to the Power Platform Admin center as a System Administrator
Go to Environments, select the needed environment and open the Settings page
In the Settings page, go to Users + permissions, and select Application users
In the application users page, click + New app user to open the Create a new app user page
You will be able to add a registered Azure AD application that was created for the selected user by clicking + Add an app
Select the App and click Add
Check this article for more information on how to create an Azure AD application
After you select the App, select a business unit from the dropdown list
In the Security roles section, select the needed roles and then click Save
Click Create to add the Application User
Once the Application user is created, you can perform the below Actions
- Details: will allow you to check the details of the Application user and apply specific changes
- Edit Security Roles: will allow you to add/remove security roles to/from the Application user
- Deactivate: will allow you to deactivate the Application user
The Details page shows the below properties for the application user noting that only the business unit, email address, and security roles can be edited:
- Name
- Azure AD application ID
- Assigned security roles
- App type
- Business unit
- Email address

Hope This Helps!

CALL JAVASCRIPT FUNCTION ON SUBGRID REFRESH IN DYNAMICS 365

noreply@blogger.com (Charles Abi Khirs) — Mon, 27 Jun 2022 07:08:00 +0000

In this post, we will see an example on how to call JavaScript function when a subgrid is refreshed in Dynamics 365.

Sometimes, you have a scenario where you need to call a JavaScript function when a sub-grid refresh event has occurred in the form.

The subgrid refresh event might happen if a record is added to the subgrid, deleted from the subgrid, or the refresh button of the subgrid is clicked.

In order to trigger the function, you have to register a function on the OnLoad event of the form (in the below exemple manageFormBasedOnRecordsInSubgrid) which in turns, will call the OnLoad event of the subgrid
After doing this, each time you add/delete record from sub-grid, the function functionTriggerredgetOnSubgridRefresh() will be triggered.
Below, is a sample code for the function that will be called when the subgrid is refreshed
var formContext;
var gridContext;
function manageFormBasedOnRecordsInSubgrid(context) {
formContext = context.getFormContext();
gridContext = formContext.getControl("Contacts");
//ensure that the subgrid is ready…if not wait and call this function again
if (gridContext == null) {
setTimeout(function () { manageFieldsBasedOnLivrableSubgrid(); }, 500);
return;
}
//bind the event listener when the subgrid is ready
gridContext.addOnLoad(functionTriggeredgetOnSubgridRefresh);
}

function functionTriggeredgetOnSubgridRefresh() {
try {
setTimeout(function () {
if (gridContext != null && gridContext != undefined) {
var recordsCount = formContext.getControl("Contacts").getGrid().getTotalRecordCount();
if (recordsCount > 0) {
var alertMessage = { text: "Do something here when subgrid contains records" };
Xrm.Navigation.openAlertDialog(alertMessage, null);
}
else {
var alertMessage = { text: "Do something here when subgrid has no records" };
Xrm.Navigation.openAlertDialog(alertMessage, null);
}
}
}, 1000);
}
catch (e) {
var alertMessage = { text: "getTotalGridRecordCount Error: " + e.message || e.description };
Xrm.Navigation.openAlertDialog(alertMessage, null);
}
}

Hope This Helps!

TURNING OFF SEND ERROR REPORT IN DYNAMICS 365

noreply@blogger.com (Charles Abi Khirs) — Mon, 13 Jun 2022 08:22:00 +0000

In Dynamics 365, when errors occur in the product, users have the option to send error reports to Microsoft about the error.

The error report will contain data that can help Microsoft fix these problems and improve the products and services.

A pop-up will be displayed to the user that will be able to select the needed option

In this post, we will see how to turn off sending error reports to Microsoft.

In order to change the error reporting preferences, you can follow the below steps

Open the Power Platform admin center and go to Environments
In the list of Environments, select the specific environment and open the Settings
In the Settings page, under the Product settings section, click Privacy + Security
In the Privacy Preference page, under the section Default action to take when an error occurs, select the option Never send an error report to Microsoft
Click Save to apply your changes

Hope This Helps!

CREATE DYNAMICS 365 ENTITY IN SDK

noreply@blogger.com (Charles Abi Khirs) — Mon, 06 Jun 2022 06:31:00 +0000

In this post, we will learn how to create a Dynamics 365 custom entity in SDK and how to set some of its properties.

The below function can be used to create a custom entity

public void CreateEntity()
{
CreateEntityRequest createrequest = new CreateEntityRequest
{
Entity = new EntityMetadata
{
SchemaName = "cak_CustomEntity",
DisplayName = new Label("Custom Entity", 1033),
DisplayCollectionName = new Label("Custom Entities", 1033),
Description = new Label("Custom entity created using SDK", 1033),
OwnershipType = OwnershipTypes.UserOwned,
IsActivity = false,
IsBusinessProcessEnabled = true,
IsAuditEnabled = new BooleanManagedProperty(true),
IsSLAEnabled = false,
},
PrimaryAttribute = new StringAttributeMetadata
{
SchemaName = "cak_name",
RequiredLevel = new AttributeRequiredLevelManagedProperty(AttributeRequiredLevel.None),
MaxLength = 100,
FormatName = StringFormatName.Text,
DisplayName = new Label("Name", 1033),
Description = new Label("Primary attribute for the custom entity.", 1033)
},
HasActivities = true,
HasNotes = true,
SolutionUniqueName = "CAK",
};
try
{
var result = AdminService.Execute(createrequest);
if (result.Results != null)
Console.WriteLine("Custom Entity successfully created!");
}
catch (Exception e)
{
Console.WriteLine($"Error while creating the custom entity. \n\rError message: {e.Message}");
}
}
Based on your needs, you can add or remove the properties you want to set for the entity you want to create or its primary field
If you want to add the created entity to a specific unmanaged solution, you can set the solution name accordingly in the SolutionUniqueName property

Hope This Helps!

Dynamics 365 Education and Knowledge

How to Remove an Active Unmanaged Layer from the Ribbon in Power Apps (Dynamics 365 CRM) Using ribbondebug=true

🔍 What Is an Unmanaged Layer?

🎯 Why Remove the Unmanaged Layer?

🧠 What Is ribbondebug=true?

⚠️ When to Use This

🛠️ Steps to Identify and Remove an Unmanaged Ribbon Layer

Step 1: Open Your Model-Driven App with Debug Mode Enabled

Step 2: Inspect the Ribbon

Step 3: Command Checker pane

Step 4: Check the Unmanaged Layer

Step 5: Remove the Unmanaged Layer

Step 6: Regenerate ribbon metadata

💡 Best Practices

🧪 Example Use Case

✅ Summary

DYNAMICS 365 CRM ADDING ENTITY METADATA AFTER ADDING THE TABLE TO A SOLUTION

DYNAMICS 365 CRM HOW TO CHECK THE IMPORT SOLUTION PROGRESS

Importing solutions to the DEV, TEST, UAT or PROD environments in Dynamics 365 CRM is a common activity for system administrators and developers. However, when importing large or complex solutions, it can be frustrating to sit and wonder: How far along is the import? or Is it stuck?

HOW TO GET MICROSOFT DYNAMICS 365 FORM TYPE IN JAVASCRIPT

DISABLE ALL FORM FIELDS IN DYNAMICS 365 USING JAVASCRIPT

To make the form read-only in Dynamics 365 you have 3 options: changing record status to Inactive, Business rule, JavaScript. The purpose of this article is to know how to make all form fields disabled with JavaScript.

CHANGE ROLLUP FIELD RECURRENCE SCHEDULE IN DATAVERSE / DYNAMICS 365

One of the features in Dynamics 365 is the rollup field type where you can perform aggregation and calculation of data in a parent record based on child records. You create a rollup field by adding a new field, choosing the field and data type, and building the logic for the calculation.

OPEN DYNAMICS 365 ADVANCED FIND BY DEFAULT IN DETAILED MODE

SEARCH BY GUID IN DYNAMICS 365

Is it possible to search for a CRM record using its GUID ? Well, NO it is not possible and YES it is possible!!!

SAVE FORM IN DYNAMICS 365 JAVASCRIPT

In Dynamics 365, you may need to save a CRM form automatically in JavaScript upon a specific action on the form.

CHANGE CONTROL LABEL DURING RUNTIME IN DYNAMICS 365 USING JAVASCRIPT

In Dynamics 365, we might have to change CRM control label at runtime for specific needs. This can be easily done through JavaScript code by calling the function setLabel() that sets the label of the control.

CHECKING DIRTY FIELDS IN DYNAMICS 365 USING JAVASCRIPT

SET DYNAMICS 365 MULTISELECT OPTIONSET FIELD IN C#

SETSUBMITMODE IN DYNAMICS 365 JAVASCRIPT

ACCESS FIELDS OF QUICK VIEW FORM THROUGH JAVASCRIPT IN DYNAMICS 365

FILTER LOOKUP IN DYNAMICS 365 BASED ON CONDITION IN JAVASCRIPT WITH ADDCUSTOMFILTER AND ADDPRESEARCH

DISABLE SECURITY DEFAULTS FOR DYNAMICS 365 ENVIRONMENT

GET THE SIZE OF DYNAMICS 365 TABLES FOR ON PREMISES ORGANIZATION

In previous post, we saw how to get the size of Dynamics 365 / Dataverse tables for an online environment In this post, we will see how to get the size of Dynamics 365 tables for an on premises organization.

GET THE SIZE OF TABLES IN DYNAMICS 365 / DATAVERSE ENVIRONMENT

SELECT ALL OPTIONS OF MULTISELECT OPTION SET (CHOICES) FIELD IN DYNAMICS 365

DATA CENTER REGIONS FOR DYNAMICS 365

CHANGE USER BUSINESS UNIT WITHOUT REMOVING SECURITY ROLES IN DYNAMICS 365

CREATE APPICATION USER FOR DYNAMICS 365

CALL JAVASCRIPT FUNCTION ON SUBGRID REFRESH IN DYNAMICS 365

TURNING OFF SEND ERROR REPORT IN DYNAMICS 365

CREATE DYNAMICS 365 ENTITY IN SDK

In this post, we will learn how to create a Dynamics 365 custom entity in SDK and how to set some of its properties.

🧠 What Is `ribbondebug=true`?

Importing solutions to the DEV, TEST, UAT or PROD environments in Dynamics 365 CRM is a common activity for system administrators and developers.

However, when importing large or complex solutions, it can be frustrating to sit and wonder: How far along is the import? or Is it stuck?

To make the form read-only in Dynamics 365 you have 3 options: changing record status to Inactive, Business rule, JavaScript.

The purpose of this article is to know how to make all form fields disabled with JavaScript.

One of the features in Dynamics 365 is the rollup field type where you can perform aggregation and calculation of data in a parent record based on child records.

You create a rollup field by adding a new field, choosing the field and data type, and building the logic for the calculation.

Is it possible to search for a CRM record using its GUID ?

Well, NO it is not possible and YES it is possible!!!

In Dynamics 365, we might have to change CRM control label at runtime for specific needs.

This can be easily done through JavaScript code by calling the function setLabel() that sets the label of the control.

In previous post, we saw how to get the size of Dynamics 365 / Dataverse tables for an online environment

In this post, we will see how to get the size of Dynamics 365 tables for an on premises organization.