Introduction: In this blog, we shall see how can a user install multiple Portal Instances for Microsoft D365 CRM Online. Pre-Requisites: D365 CRM Portals D365 CRM Environment Overview 1. A user can set up more than one Portal for a given D365 Environment provided that the second portal is different from the first portal that is installed. For eg: If the user has already installed a community portal then the user will have to install a different type of portal like partner portal , employee portal etc. 2. The user cannot install two portals of the same type. For eg. If the user has already installed a customer portal then he cannot install multiple portals which are customer portals. 3. As we know that a user can have multiple portals associated with the same D365 (CRM) instance and along with a single D365 Subscription the user gets out of the box a single portal license, which means that the user gets only one free portal add-on. 4. The user can go to the Instance page and install multiple portals as shown below in the available multiple options. In order to have a second portal add-on on the D365 instance the user will have to follow the Steps given below: Step 1: Opening the Admin Center.  Go to D365 and open admin as shown below. Step 2: Opening the Purchase Service In the Admin Center Page click on the Billing option in the left side menu bar and select Purchase Services under that. Step 3: Selecting the Subscription In the Purchase Services, we will have to find the following subscriptions which are as follows: Dynamics 365 Enterprise Edition – Additional Portal Dynamics 365 Enterprise Edition – Additional Portal Page Views **Note: These Licenses are only shown to the user if they have a purchased license and are not using trial version of the license

Introduction: This blog explains how to configure Create Customer Assets Page in D365 Partner Field Service Portal. Steps of Implementation: 1. Create a new Entity Form in D365 Field Service. Create a new Form for Customer Asset Entity with name “Portal Customer Asset – Create” and publish as shown below. Create Entity Form with name “Create Asset” as shown below. Open “On Success Settings”, set On Success as “Redirect” and Web Page as “Assets” as highlighted below. Set Submit button on Entity Form, Click on “Submit” Action and enter label as “Create Asset”, as shown below. Create a new Entity Form Data to set “Expose to Customer” equals “True”. Select Type as “Attribute” and select Attribute Logical Name as “Expose to Customer”. Check on “Set Valule on Save”, select Type as “Value” and enter Value as “true”. 2. Create a new WebPage in D365 Partner Field Service Protal. Open Assets Page. Click on New => Child Page in Administrative Panel. Enter details as below and click on Save button. 3. Add Create button in Assets Entity List in D365 Field Service. Open “Assets Customer Web View” record in  Entity List as highlighted below. Open Grid Configuration Section in Options Tab. Create new Action “Create”, Select Target Type as “Web Page” and select Redirect to WebPage as “Create Assets ( Partner Portal )” as shown below. Conclusion: Above description in blog helps users to create Customer Assets from D365 Partner Field Service Portal. Create button on Asset List Page. Create Asset form. New Asset record is shown in list. Blog Tips: How to redirect to page after a record is created successfully by using “On Success Settings” tab. How to set data on record from D365 Portal automatically by using Entity Form Metadata. How to show data created in D365 Field Service Portal as soon as it is created by setting field “Expose to Customer” equals to true.  

For the modern-day organisations that have global scalability and digital intelligence, dynamics 365 for finance and operations is definitely the need of the hour. Make more precise interest estimates to improve your items’ accessibility and limit your stock expenses. The apparatus utilizes Microsoft SQL Server determining calculations, Microsoft Excel perceptions, and Dynamics 365 for Finance and Operations models—for conjectures you can rely on. Get perceivability across associated circulation, client assistance, deals, and promoting frameworks so you can develop your items and procedures to meet rising desires.  Get continuous data on practically any gadget, whenever. Elements 365 for Finance and Operations improves and quickens business process changes. What’s more, it’s situated in the cloud, so it coordinates with inheritance frameworks and scales universally effortlessly Introduction: Job is collectivity of tasks and responsibilities which are required of worker who perform a job. Pre-requisites: Before setup jobs, need to create below elements: • Job Title • Job Function • Job types • Compensation level • Survey company • Skills and skills level • Certificate type • Test type • Education • Screening type • Job tasks • Areas of responsibilities Steps: Below are steps to create department- Click Human resources > Jobs > Jobs. Click New In the Job field, enter a name for the job. In the Description field, type a brief description of the job. In the Title field, select a title for the job. In the Maximum number of positions field, indicate the number of positions that are allowed for the job: Maximum positions – Select this option and enter the maximum number of positions that are allowed for the job. Unlimited – Select this option to indicate that an unlimited number of positions are allowed for the job. In the Full-time equivalent field, enter an employment factor from 0 to 1. The value 1 indicates a full-time job. For part-time employment, enter a number between 0 and 1. For example, enter .5 for a half-time job. In Description Fast tab, enter detail description of the job. Click on the Job classification fast tab In the Job type field, select a job type to associate with the job. In the Function field, select a job function. Click on Compensation fast tab. In the Level field, select a wage level for the job. In the Survey company field, select the survey company that is responsible for the survey that was applied to establish the market-based pay range for this job. In the Reference job field, enter the job code that the survey company uses for this job. In Market Price Range information, specify market based pay range in source field. In Low threshold, control threshold and high threshold, specify minium, basic and maximum amount that paid to worker who assigned for this job. On Skills fast tab, enter skills required for the job. In level field select skills level and in importance field, select importance level (From1 to 6) On the Certificates fast tab, optionally enter certification requirements for the job and importance of the certificate On the Tests FastTab, enter tests for workers are required to pass for the job. On the Education FastTabs, optionally enter educational requirements for the job and the importance of the education. On the Screenings FastTab, optionally enter any screening that workers are required to pass for the job. On the Job tasks FastTab, optionally enter job tasks to the job template. On the Areas of responsibility FastTab, optionally enter areas a worker is responsible for in jobs. Conclusion: By attaching job to position you can assign position to worker and it will help to maintain and track Job tasks, responsibilties, Skills, education, certifications, tests.

Introduction: This blog consists of steps to change the name of the custom app in Dynamics 365. Initially the app name is “Dynamics 365-custom” as shown below. Steps: We can change the name to our organization name as shown below: Navigate to Settings–> Administration–>System Settings In General Tab–> Set options for the default app:Dynamics 365-custom–>Change the default app name The App name is changed to “CloudFronts Apps” and will be visible as below: Conclusion: Like this way, you can change the name of custom application in Dynamics 365.  

Introduction : In AX 2012R3 Commerce Data Exchange, Async Server is a part of the asynchronous system that shares data between the Microsoft Dynamics AX database and channel databases. Async Server is installed at headquarters and communicates with Microsoft Dynamics AX. In addition to Async Server, Commerce Data Exchange includes Commerce Data Exchange: Async Client, which is installed at channels and communicates with the channel database. Below are the steps which need to follow: Step 1: Start Microsoft Dynamics AX Setup. Under Install, select Microsoft Dynamics AX components. Advance through the first wizard pages. If the Setup Support files have not yet been installed on this computer, the Select a file location page is displayed. The Setup Support files are required for installation. Provide a file location or accept the default location, and then click Next. On the Ready to install page, click Install. Step 2: On the Select installation type page, click Custom installation, and then click Next. On the Select components page, select Async Server, and then click Next. Step 3: Prerequisite validation results page, resolve any errors. For more information about how to resolve prerequisite errors. When no errors remain, click Next. Step 4 : Configure Async Server page, select the check box to configure Async Server by using Setup. If you clear this check box, the application files are installed, but Async Server is not configured. If you’re configuring Async Server, enter the following information: Application name – The name of the web application that hosts Async Server. App pool name – The name of the application pool that the web application runs under. Website name – The name of the website that Async Server runs on. User name and Password– The credentials for the application pool identity. HTTPS port – The port on which Async Server receives HTTPS requests. You can specify any available port. Verify that the port is open in Windows Firewall, and record the port number. The port is used to create the URL for Async Server in the following format: https://<server name>:port/<web application name>. This URL is required when you configure instances of Async Client that connect to this instance of Async Server. TCP port (optional) – The port on which Async Server receives TCP requests. Specify a TCP port if your environment uses high-performance data synchronization. You can specify any available port. Verify that the port is open in Windows Firewall. AOS service user – The user account that the instance of Microsoft Dynamics AX Application Object Server (AOS) runs as. SSL certificate thumbprint – The thumbprint for the Secure Sockets Layer (SSL) encryption certificate. You must obtain a valid, registered certificate from a provider. Step 5: Select Server Name and Message Database Name. if DataBase does not exit then mention the Name. Setup will create the database. Step 6: the Prerequisite validation results page, resolve any errors. For more information about how to resolve prerequisite errors. When no errors remain, click Next. Step 7: Click on Install button. Conclusion: By following above steps, you can install Async Server for Retail HQ.

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: 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 “&amp;” 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(/&amp;/g, ‘&amp;amp;’); 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.