Introduction: Finally, one of the most sought after feature is here in the D365 July 2017 Update. The Multi-Select Option Set! A new attribute type added to D365, you can now create Multi-Level OptionSets in D365. Creating a Multi Select OptionSet: A new attribute type is now available that lets you create Multi-Select Option Set. 1. When you create a new field, you’ll see an option to create a Multi-Select Option Set. 2. Here, I’m creating an Option Set for choice of Subjects for Newsletter Company. I’ve named the field as Subjects and I’ll let users select which all subjects is a particular customer interested in in the Enrollment entity. 3. The Multi-Select Option Set looks like a usual option set and my options look like this 4. And I’ll add the same in my form as well and Publish all my changes. Using Multi-Select Option Set: Below is how you can select multiple values in the Multi-Select Option Set. Once on the form, here’s how you can use the Multi Select Option Sets 1. They come with auto-complete feature, so you can start typing the options and they will show up 2. Now, I have selected 3 options namely Technical, History and Science and my subject of interests. 3. Once selected, they appear separated by semicolon (;) And I’ll save the record. Multi Select Option Set on Views: You can see selected values in the Multi-Select Option Sets on the entity views as well. Some Features: Below are the features of the Multi-Select Option Sets Auto-complete the results. Can hold up to 150 values Can be used in Advanced Find as well as FetchXML queries. Hope this was helpful!  

Introduction: This blog focuses on displaying the captions of all action buttons of NAV Pages in Arabic language. The requirement was such that the user wanted to view Microsoft Dynamics NAV in Arabic. To suffice this, we installed Arabic module for Microsoft Dynamics NAV 2017 RTC, Server and web client. After installation, only the standard functions e.g New are converted into Arabic language. other functions, buttons are viewed in English. Hence, we need to change the caption labels of these buttons, text constants in Arabic. Pre-requisites: Microsoft Dynamics NAV 2017 Steps: 1. Install Arabic Module for Microsoft Dynamics NAV 2017 RTC, Server, Web Client. 2. Select the objects then Tools > Translate > Export. 3. Change the language code of English i.e 1033 to Arabic 1025. Get translation of English text into Arabic. 4. Save the text file in UTF-8 Encoding. 5. Copy the text file to C:\Program Files\Microsoft Dynamics NAV\100\Service\Translations And C:\Program Files\Microsoft Dynamics NAV\100\Service\Instances then Restart your service Conclusion: After restarting Dynamics NAV services, all the captions buttons of the Pages  appear in Arabic language.

Introduction: In reports, we always a requirement to display header rows of the table on every page. In this article, I will be explaining the steps to do the same in Dynamics NAV. Pre-Requisite: 1. Microsoft Dynamics NAV 2. Visual Studio Report design Environment Procedure: 1. Under layout of your report, click on the arrow under Column groups and then click on Advanced Mode. 2. Now click on (Static) under Row Groups section. 3. Navigate to the properties window of the (Static) under row groups which is displayed on the right. If it is not present, you can open it by navigating to View->Properties Windows or using ‘F4’ button. The properties window will then appear on the right. 4. Now, you need to modify the following properties. Set ‘FixedDate’ property to ‘True’. Set ‘KeepWithGroup’ property to ‘After’. Set ‘RepeatOnNewPage’ property to ‘True’. Using the above steps, your table header rows will be displayed on every page of your report. In the above screenshot, my table header row which includes the captions for the column i.e. row containing ‘No’ and ‘Name’ will be displayed on every page of the report.  

Introduction: While using Fetchxml queries to retrieve more than 5000 records, first page will give you 5000 records and paging cookie. Paging cookie will help to retrieve additional records. For additional records, we need to set the paging cookie in the fetch tag. Setting the paging cookie: When the fetch query is executed it brings the paging- cookie with it in the resultant response. The paging cookie is attached to the next Fetch XML The paging cookie consists of the first and last record details. Name and the GUID of the records. When trying to execute fetch XML request. it started throwing “Page Cookie Malformed” exception. This is because there is a special character present in the paging Cookie. You can see in the above cookie that Name has “&” which is the replacement for character “&”. This breaks the fetchXml request.There can be any character present in the record name such as (‘s). Even (‘) breaks the fetch XML. Thus, we need to encode the paging-cookie before it is inserted in fetchXml. pageCokies.replace(/&/g, ‘&’); This will help to solve the issue and we can retrieve more than 5000 records.

In this blog, we will see how can we upgrade the D365 online Portal to v8.3 and what are the new features that are available in this upgrade. Pre-Requisites: D365 CRM Portals D365 CRM Environment Overview: The new version 8.3 for D365 online Portals is made available in the July update provided by Microsoft. Along with the new version of portals there are some amazing new features and functionality changes which are mentioned below. User has now control over the time setting as to when was the portal upgraded Administrative wizard tile is added to the Portal module in CRM. User can now clear cache from the portal to improve the performance We will now see how the user has to upgrade the portal to the new v8.3 in the following process Process: Step 1: The user will have to go the Instance page of the Dynamics 365 Administration Center. In the Instance page click on the edit button to the side of ‘Solutions’ as shown below. Step 2: In the list of Managed solutions for the user’s organization, if the portal hasn’t been upgraded the user will see ‘Upgrade Available’ for the portal if installed previously as shown below On the left, we can see the details of the upgrade that will be applied to the existing portal solution. Click on the Upgrade button as shown to initiate the upgrading process. Step 3: On clicking on the Upgrade button user will get a prompt for Terms and Service click on ‘Upgrade’ to Proceed as shown below The user will have to wait for the upgradation process to complete. Once the upgradation process is complete, the user can check the current version of the portal by going to the following link: https://[portaladdress].microsoftcrmportals.com/_services/about. If the user has the v8.3 portals along with admin sign in can view more details of the portals  

Introduction: In this blog, we will see how can we use the new feature of the ‘Administrative wizard’ for the D365 Online Portals Pre-Requisites: 1. D365 CRM Portals 2. D365 CRM Environment Overview In the new update of D365 Online Portal for v8.3, a new feature has been introduced which is the ‘Administrative wizard’ which enables the user to customize the portal by allowing to add an entity to the portal. The user needs to decide as to which entity (i.e. a custom entity or an out of box entity) is to be added prior before adding it to the portal The administrative wizard enables the user to also add entity components like entity form, list, web pages etc. Scenario: In the following scenario, we will add a custom entity with a form and view which is configured prior to the process of adding it to the portal. Process: Step 1: To initiate the process, the user will have to navigate to Portal > Administration > Portal Management as shown below. This will start the administrative wizard. Note: The ‘Portal Management’ Tile is only visible for 8.3v of D365 Online Portals. Step 2: Now select ‘Create Portal Content’ from the two options under Portal Management as shown below. A dialog box will appear after selecting the above mentioned option which will allow the user to create a web page and to display a entity which is optional depending on the requirements of the user. Step 3: In the dialog box the user will have to enter the following details like the name of the portal website, page name, title, layout and partial URL. Select the publishing state as ‘Published’ as shown below. The user can get additional options on enabling the entity in the page by changing the value of the ‘Display Organization entity in the portal’ to ‘Yes’ which is ‘No’ by default. On selecting Yes the following options appear as shown below: 1. The user can select the entity from which he would want to use a particular view. 2. Select the view that is to be displayed. 3. Finally select the Form that is to be displayed. The user wants can allow record creation and anonymous access by toggling on the options to ‘Yes’ or ‘No’. Once all the details have been entered click on the create button to the bottom of the dialog box. Step 4: The user will be automatically redirected to the Portal> Web Page option in CRM where a Web Page is created which consists of the entity list details entered in the previous step. In the Child page section will include the create, edit and details web pages with entity forms associated with it as shown below. Conclusion: Thus, by using administrative tool we can create and expose entity information effortlessly and easily on the D365 Online Portal.

Introduction: This blog explains how to set Customer Type field in D365 Javascript Web API. Problem Statement: We get error while setting value of Account lookup on Contact in D365 Javascript Web API as below: “An undeclared property ‘customerid’ which only has property annotations in the payload but no property value was found in the payload. In OData, only declared navigation properties and declared named streams can be represented as properties without values.” Solution: We can achieve this functionality by adding suffix entity name to the schema name of the field. Steps of Implementation: Below code demonstrates how to set Account on Contact. entity[“parentcustomerid_account@odata.bind”] = “/accounts(” + Account_GUID + “)”; Below code demonstrates how to set Contact on Contact. entity[“parentcustomerid_contact@odata.bind”] = “/contacts(” + Contact_GUID + “)”; Note: This issue arises when lookup attribute of the entity can accept multiple types of entity references below are common examples 1. Customer on Incident 2. Customer on Contact 3. Customer type field on Custom Entity. Conclusion: We can resolve issue for setting Customer type field in Javascript D365 Web API by adding suffix entity name to the schema name of the field.

We do have many different development and deployment Environment and we do have different configurations with respective to the environments. These configurations may be tricky but it provides ease to user to deploy to different environment without changing configurations again and again. Below are the screen shots that will help to setup these configurations. Let’s create one more environment, let’s call that QA. Now you can see QA also in the environment. Let’s now create project parameters and configure it against environments. After creating few project parameter, we can configure it. Then you assign values to parameter with respect to environment. Then Click OK. When you click ok you can see the values assigned to the parameter. Let’s change the environment to QA, and you can see the change in the parameter. This kind of parameter we can use in the expression in different package, so we just need to change at one place.

Introduction: Sometime it requires us to update only certain records which satisfies condition. so how to update those records all at once. Description: We had a requirement where we wanted to change the status of all the record of lead which are in New status. We need to follow below steps to achieve this. Make sure that your search field is added on Quick find view of that entity, otherwise you will not find the record in quick find view. in our case it is lead entity. Added the column status. Save and publish your customization after adding the column. Let’s go the home page of lead entity and search by putting criteria “new”, it will list down all the records which matches the condition. Now you have all the records that matches the condition of new means these records are newly created. Now click and edit in online excel as shown. Now you can edit any column listed. In our case I have changed the status from new to approved of two records, as it shows it is processing two records as shown. Record is updated/ failed in system you can see it as shown below. You can open and see the changes in that records. Hope this helps you while doing bulk update for the records based on condition.

This blog consists of steps to add an external link to navigation bar in the application using new sitemap editor in Dynamics 365. Steps to be followed are given below: Create an HTML Web Resource in CRM consisting of below code. <html> <body> <script> //open link in new window window.open(“https://www.google.com”); </script> </body> </html> Open the sitemap editor and add a new subarea and the created web resource into your sitemap Publish your configurations and click on Google Search in the Navigation to check the results: Behaviour: On click on the link, the link opens in the new tab.