Dynamics 365 Education and Knowledge

In this quick post, I will talk about a limitation you might face when working in D365 CE which is exceeding the maximum number of link entities in a query . The exception message that you will receive is the following: Error : Number of link entities in query exceeded maximum limit. where the maximum number of link entities is 10. You get this error in different scenarios In a view when you add fields of more than 10 related entities because they are reflected as link entities with outer join to the main entity <OrganizationServiceFault xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/xrm/2011/Contracts">......... <Message> Invalid FetchXml on SavedQuery.Update. </Message>......... ...

Let's take the scenario, where a user has to choose Department 1, Department 2 and Department 3 on a form for escalation purpose. Each department has its own enabled and required fields where a user in the department has to fill before saving. In this situation, when you have multiple attributes on the form that operate similarly, and if needed, as a best practice, they should fire the same JavaScript function. In order to achieve this, you need to dynamically get the attribute name of the field being changed ( source of the event ) in the function to know which dependent fields should be enabled and set as required. Here comes the role of the getEventSource() function by calling it as follows formContext.getEventSource().getName(); that will retrieve the schema name of the field being changed, and this way, you can achieve some work based on it as per the below function. ...

Dynamics 365 product team is always working to improve and give the best user experience. Therefore, the continuous evolutions of the different areas and possibilities are one of the most critical things to bring. In this post, I will talk about one of these user experience improvements which is Reference Panel that was introduced with the Dynamics 365 V9. So what is exactly a Reference Panel? The Reference Panel is a type of section that can be added to the form that allows users to move across different types of sub grids and quick view controls in a single place without scrolling down or up. Let's take the example of the account form, where many quick view forms and sub grids exist inside (contacts, recent cases and opportunities...). When the users enter the form, they have to scroll up and down through the form in order to check the sub grids and their data which is sometimes annoying for them. ...

In this previous post , I described how to show a global notification in the model-driven app from within an event handler on the form and we saw the different options and possibilities that we can do with this functionality. In this post, I will show you how to display a notification from any entity view instead of the form level. For example, if you want to show the number of pending tasks to the user or the number of opened opportunities that should be closed and maybe allow the user to click the action button and be redirected to the appropriate screen. Let's see how! First, create a new solution and add the Application ribbon component in it From the Ribbon Workbench, open the solution Scroll to the right, and add a new button under the Home menu in Mscrm.Hom...

The function setFormNotification() is used to display a notification message as information, warning or error message on the form and it lives within the form itself. Once you navigate outside the form, the notification will be gone. In other post , I described how to show a global notification from an entity view. However, in this post, I will show you how to display a global notification that will be displayed across the Model driven App and not limited to the form. To do this, you can use the function Xrm.App.addGlobalNotification(objNotification).then(success,error) that will display a warning, error, informational, or success message. In addition, it will give the user the possibility to close the notification and perform a specific action that will be executed based on the notification. To implement this, you can call the function that disp...

In this quick post, I will describe a strange issue I have faced on CRM on-premises V9 in a quick view with a sub-grid component in it. Most of you have worked with quick views and you know that you can add a sub grid in it to display records related to a specific record selected in a lookup field. PROBLEM When a lookup field is selected and its related quick view has appeared, the sub-grid existing in the quick view is blank and never loads as displayed in the below screenshot. REASON The tab containing the quick view with a sub-grid is collapsed by default SOLUTION Put the tab as expanded by default, and after save and publish, the sub-grid in the quick view is properly shown. Hope This Helps!

In this quick post, I will talk about a display issue of the ribbon buttons. After upgrading from D365 V8.2 to D365 V9 (9.0.16.7) on-premises, there is abnormal white space around the ribbon buttons . This behavior was everywhere whether in the views, forms or other areas. Opening the interface in different browsers have the same behavior; therefore, it is not a browser issue. When opening the Ribbon Workbench, the buttons are properly displayed without any white space. The last try is to apply the latest update of the D36 V9 on premises, and after it is completed, the buttons are properly displayed and no white spaces exist anymore. Hope This Helps!

Since the introduction of the Business Rules as a new functionality in Dynamics 365, it becomes the recommended way to be leveraged against writing client-side code whenever it is possible. By using this approach, it will become more maintainable and supportable for further upgrades of the environment and will reduce time spent on code management and compatibility before/after the updates. However, there are situations where you cannot fully apply your needs in a Business Rules due to the complexity of the need or limitation in the Business Rules. Therefore, you have to get back again to JavaScript. In this post, I will talk about one of those limitations in Business Rules which is related to Multiselect option set fields . Unfortunately, when you have a multiselect option set field, you cannot use it as part of the Business Rule condition or within the available actions, even if you wan...

In this post, I will mention some of the events that are used against Business Process Flows . Even though these events are executed from the form context, but, they are not registered directly from the form editor like On Load, On Save, On Change events. Instead, these events can be registered and called from the JavaScript while loading the form in the OnLoad event of the form. Below are some of the BPF events that can be registered: OnPreProcessStatusChange : This function will be executed before the BPF status changes and can be called as follow formContext.data.process.addOnPreProcessStatusChange(functionName) OnPreStageChange : This function will be executed before the BPF stage changes and can be called as follow formContext.data.process.addOnPreStageChange(functionName) OnProcessStatusChang...

In another post , we saw how to debug a plugin using Profiler and highlighted a downside of this method which will not give you a real-time state of the Dynamics 365 database you are working on. However, in this post, I will show you how to debug a plugin in real-time of the execution of the plugin itself using the Visual Studio remote debugger tool . This method will only work for On-premises environments since you should install and run the tool on the CRM server. The below steps will teach you how to debug the plugins First things first, you have to download the remote debugger tool using this link based on the Visual Studio version you are working with Once the download is done, copy the installer on the CRM server and double click to install it ...

Most probably, you have faced a scenario where you need to block the user from interacting with the form and you want him to wait a little bit until a process is completed and then he can work again on the form. However, blocking the user from working without informing him that something in the background is being processed is not a pretty thing to do. Therefore, and to avoid this misunderstanding, you can display a loading dialog to inform him of this behavior, so he knows that he should wait a little bit before resuming the work on the form. To achieve this, there is a straight forward method to do it, which is by using the Xrm.Utility.showProgressIndicator("Processing... Please wait!!!") method in the JavaScript. You can add this line of code in any function, where you want to block the user from interacting with the interface while you are waiting for a process to be completed. Once the pro...

In this previous post, we have learned how to create, structure and organize the Dynamics 365 Web Resources files . In this post, we will learn how to add and use namespace in Dynamics 365 JavaScript web resource and how to call the functions. In the JavaScript web resource, add your specific namespace as per the below code var CAKBlog = CAKBlog || {}; //Create CAKBlog namespace CAKBlog.Form = CAKBlog.Form || {}; //Create CAKBlog.Form namespace CAKBlog.Form.Account = function () { //Create CAKBlog.Form.Account namespace //Functions are added here }(); Add your functions' logic inside, noting that these functions are private and cannot be directly called CAKBlog.Fo...

PROBLEM Last day, I was working with D365 V9 on-premise and I have encountered a weird issue where a section was overlapping on another section side by side. It was very strange since all the fields in this section are having the same behavior. The special thing about this section is, that it contains many html web resources and other fields that are being hidden using JavaScript, and the issue occurs in the edit form. When the web resources are displayed on the create form, the issue is not there and everything seems normal. REASON After some digging in the html to see what might be the issue, I noticed that the section (table in the generated html) with the erroneous behavior has a style table-layout : auto, if I set it to fixed (in the developer tool - F12), the section is normally displayed and the overlapping is gone even when I resize the window. However, this soluti...

Everyone knows that Xrm.Page is deprecated and it is replaced by the executionContext.getFormContext() method, where the execution context is passed from the form as the first parameter to the function you are calling (reference link ). In the same above link, it is mentioned that Although Xrm.Page is deprecated, parent.Xrm.Page will continue to work in case of HTML web resources embedded in forms as this is the only way to access the form context from the HTML web resource . However, you can access the form context from HTML web resource without using Parent.Xrm.Page and this is the topic for today. You have to create a function that will return the formContext , then, on load of the form call this function, and finally call this function from the web resource. Declaration of a variable and function that return the formCont...

When adding a sub-grid components on a form, the sub-grid will have many action buttons that are displayed in the top right corner like the New Record button and the Open Associated View button. This post will focus on how to Show Hide the Open Associated View button The function of this button is to open the displayed records in the associated view. Sometimes you need to hide this button while other times it is hidden and you want to show it. So what is the reason of this behavior and how to show / hide this button I will work on the Account > Contacts relationship to clarify this behavior where the button is displayed on the Contacts sub-grid of the Account form In order to show the button in the contact sub-grid, you have to add the contact entity to the navigation area of Account form and remove the contact entity from the navigation ...