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 document contains the steps on how the TIBCO Cloud Integration Agent with custom connector for Dynamics GP can be deployed on server. Install a TIBCO Cloud Integration on-premise agent A TIBCO Cloud Integration agent needs to be installed on the server where the target data store resides. Download TIBCO Cloud Integration agent You can download and setup an agent from https://app.scribesoft.com Once logged in to TIBCO Cloud Integration portal in the server where the target data store resides, navigate to ‘More’ and then ‘Agents’ and then click on ‘+’ and ‘On-Premise Agent’ to create a new agent. Please refer the screenshot below: A new window will open where you can click on Install On-premise Agent to download the agent as shown below: On clicking Install On-premise Agent, TIBCO Cloud Integration will provide you to download the agent. You need to save the same to your local system. Copy the Agent Key in your clipboard; it will be used during Installation of Agent. Navigate to the location where the ScribeInstaller was downloaded and start the installation Make sure pre-requisites are setup to be able to successfully continue with the installation and click Next:   The wizard will start. Click Next until you see the screen where Agent Key is asked by the installer. Enter the same key which appeared on the screen where new agent was provided to be downloaded. And click next. Select where you want to install the TIBCO Cloud Integration agent. Finally click Install Agent. Let the setup continue. Click Finish once the setup completes.   Turning TIBCO Cloud Integration Agent on and off TIBCO Cloud Integration Agent on your system is a Windows Service which can be stopped, started and restarted. View Services application on your Windows machine to locate the TIBCO Cloud Integrationweb service Locate Scribe Online Agent in the Services. This is where you can start and stop service in the event of updating the DLLs for the Scribe Online connector. Deploying Scribe Online connector on the target system Deploying the Scribe Connector to the target system consists of copying the required DLLs and PDBs to the following folder in the Scribe Online Agent directory located on the target machine: Locate Connectors folder in the Scribe Online Agent directory. Folder named “DynAD Connector” contains DLLs and PDBs required to be available in the Scribe Online’s Connector folder. This folder needs to be copied in the Scribe Connector’s Connector folder. The address for Scribe Online Connector is: C:\Program Files (x86)\Scribe Software\Scribe Online Agent\Connectors Once the folder is pasted to the Connector folder, the agent needs to be started again. Navigate to View Local Services on the machine and locate Scribe Online Agent and start the same as shown below. For the Custom GP Connector developed for AKA, the following files are required to be copied in the “DynAD Connector” folder. Note: Since the project is divided into 2 DLLs across a Visual Studio solution, CFS.Connector.GPConnector.dll and CFS.GPClient.dll are the 2 DLLs and their respective PDDs are required. Required Files: Connector.GPConnector.dll and CFS.Connector.GPConnectorA part of the GP connector (.dll) and its PDD file GPClient and CFS.GPClientA part of the GP connector (.dll) and its PDD file Core.ConnectorApi.dllThis .dll file is required by the ScribeOnline agent to be able to access the Scribe API provided by ScribeOnline. Json.dll and Newtonsoft.Json These .dll files are required by the connector to be able to JSON file stream where the fields of the target connector are retrieved. JSON files – 5.1 DynADCampaignHeader.json 5.2 DynADCampaignLineItem.json 5.3 DynADSalesCommission.json 5.4. DynADCampaignErrorLog.jsonThe above files are the JSON files which contain the fields required by Dynamics GP entities. These files need to reside in the folder as the .dll require these. Important: These files also need to be present in the C:\Windows\System32 of the system. Updating Solutions with newly installed Scribe Online Agent Login to Scribe Online Portal through https://app.scribesoft.com Open a Solution and resign the Solution with newly installed Agent. Repeat this for all the Solutions. Conclusion: By following the mentioned steps, you can deploy the Scribe Online Agent with custom connector for Dynamics GP on server.

Microsoft power BI is a collection of features and online services that enables you to share your findings, analyse and visualise data in the form of dashboard and reports and the whole process is termed as power bi analytics. Utilizing the Microsoft Power BI Integrations, you can import information that is huge from different sources into the Power BI work area. You can alter the information or plan on changing it in the wake of bringing in to your framework.  The Microsoft Power BI Service now and then is alluded to as Power BI or app.powerbi.com. You can keep awake to date with all the fundamental data that truly matters to you. Force BI arrangement will assist you with conquering the greater part of the issues you are looking for effortlessly.  Introduction: In this article, we will see how to embed Power BI in Microsoft Dynamics 365 Operations. Steps: Register your Dynamics 365 Operations as a web app on Azure AD. Open link: http://dev.powerbi.com/apps Login to your Power BI account Fill the required details: App Name App Type: Select as ‘Server-Side Web app’ Enter a redirect URL: Your instance URL with /oauth at the end Enter a homepage URL: Your instance URL Choose API access you need. Click Register App. Once the app is registered, you will get Client ID and Client Secret. Copy these 2 keys, you will need it later. Navigate to Power BI settings in Operations which is under System Administration section.  Enter the details in Power BI configuration: Client ID: Paste the Client ID Key from Power BI registration Application Key: Paste the Client Secret key from Power BI registration Redirect URL: Your instance URL with /outh at the end Enable the Power BI Navigate to Reservation Management for instance and you will see a Power BI column. Click on Get Started. Authorize Power BI by clicking on ‘Click here to provide authorization to Power BI’ You will be redirected to the new window with authorization success message Now, you can select reports and dashboards from Power BI and pin them to your workspace.

Dynamics 365 for finance and operations is the ultimate solution for all the modern-day organisations facing issues on ERP level and this is the reason it is the most trusted software in the world which all modern-day organisations have adapted. Get a live perspective on the entirety of your numbers and information investigation from Microsoft elements for money related administrations. This cloud-based Microsoft ERP framework gives the important data you have to convey vital, information-driven bits of knowledge to key divisions. Mechanize your stockroom procedures to lessen operational expenses. With Microsoft ERP, your distribution center supervisors can all the more likely control their set aside, quality-control, and picking activities. Furthermore, with an adaptable work process motor, they can quickly react to changing business needs. Introduction This article describes how to deploy Microsoft Dynamics NAV database to Microsoft Azure SQL Database. To deploy a Microsoft Dynamics NAV database to Azure SQL Database, the database must be exported as a data-tier application (DAC) file, which is known as a .bacpac file. This can be performed by using the SQL Server Manager. Pre-requisite Microsoft Azure subscription and access to the Azure Management portal Microsoft Dynamics NAV database is installed on a SQL Server Database Engine instance. SQL Server Manager is also installed on the same computer. Access to the Microsoft Dynamics NAV installation media (DVD). Purpose: The purpose of this article is to deploy NAV Database on Azure SQL database and to access the deployed Database from Microsoft Dynamics NAV Development Environment. Steps: 1. Create and configure an SQL Database Server in Azure a. Create a SQL database in Azure. Click the New button found on the upper left-hand corner of the Azure portal. Select Databases from the New page, and select SQL Database from the Databases page Enter the Database name, resource group, select source Under Server, click Configure required settingsand click on Create a new server. Fill in the details Server name – valid server name Server admin name, password, Location. Here location is the location name where the Virtual Machine is stored When completed the form click on Select. Click Pricing tier to specify the service tier and performance level for your new database. Use the slider to select 20 DTUs and 250 GB of storage. For more information on DTU see what-is-a-dtu After selected the amount of DTUs, click Apply. Click Createto provision the database. On the toolbar, click Notifications to monitor the deployment process b. Create a server level firewall rule The SQL Database service creates a firewall at the server-level that prevents external applications and tools from connecting to the server or any databases on the server unless a firewall rule is created to open the firewall for specific IP addresses. To set a server-level firewall rule, click on SQL Database > Overview page > click Set server firewall on the toolbar as shown in the following image: The Firewall settings page for the SQL Database server opens. Click Add client IP on the toolbar to add the IP address of the computer that is currently being used and then click Save. A server-level firewall rule is created for the current IP address. Make a note of the SQL Database server name because it will be required later. 2. Deploy the existing Microsoft Dynamics NAV Database to an Azure SQL database. Deploy a databse to SQL Azure wizard is used to deploy database between an instance of the Database Engine and an Azure SQL Database server. The wizard uses a Data-tier Application (DAC) BACPAC archive file to deploy both the data and the definitions of database objects. Limitation and Restriction: The Deploy Database wizard supports deploying a database: From an instance of the Database Engine to Azure SQL Database. From Azure SQL Database to an instance of the Database Engine. Between two Azure SQL Database servers. The wizard does not support deploying databases between two instances of the Database Engine. Using the Deploy Database wizard: In the VM, open SQL Server Management studio(SSMS). Click on File > Connect Object Explorer. Connect to the location of the database you want to deploy. You can specify either an instance of Database Engine or a Azure SQL Database server. In Object Explorer, expand the node for the instance that has the database. Expand the Database Before deployment, remove the windows authenticated users as these will cause failure of the transfer process. To remove the windows login user, navigate to Security under the Database in NAV > Users >Click on the Windows user then delete. Right click the database you want to deploy, select Tasks, and then select Deploy Database to Microsoft Azure SQL Database. This opens the Introduction page, click on Next. In the Deployment settings page, click on connect and specify a path to store the .bacpac file in the Temporary file name. Specify the Azure SQL Server name, authentication is SQL Server authentication and enter the login name and password for the server and click on connect. Specify the Edition of Microsoft Azure SQL Database, Maximum database size and service objective then click on Next. This information can be viewed in the Overview of the Azure SQL Database. The progress of the deployment can be viewed in the summary tab. This may take few minutes. The Result is displayed after completion of the deployment of NAV Database to Azure SQL Database. The Database deployed can be viewed in Azure SQL database. Below is the figure showing the deployed database ‘Demo Database (10-0)’ from NAV to Azure. 3. Set up endpoints for the Microsoft Dynamics NAV client services. To add the endpoint you need to follow the below steps, Click on the Virtual Machine( VM) > overview > Resource Group . This will open an overview for the resource group. select NetSecurity (Network Security Group)  then click on  Inbound Security Rules. 4. Configure a Microsoft Dynamics NAV Server instance on the virtual machine. To configure SQL Server authentication: Set up an Encryption key Configure SQL Authentication on Database Configure SQL Server authentication on Microsoft NAV Sever Instance (Non-Multitenant) or Configure SQL Server authentication on Microsoft NAV Sever Instance (Multitenant Deployment) Follow the below steps to set up an encryption key and configure SQL Authentication on … Continue reading Deploy a Microsoft Dynamics NAV Database to Azure SQL Database →

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.  

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.

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.

Introduction: Real-time Service is an integrated service that provides real-time communication between Microsoft Dynamics AX and retail channels. Real-time Service enables individual point of sale (POS) computers and online stores to retrieve certain data from Microsoft Dynamics AX in real time. Redeem loyalty points Issue and redeem credit memos Create and update customer records Create, update, and complete sales orders Receive inventory against a purchase order or transfer order Perform inventory counts In AX 2012 R3, Real-time Service is a Windows Communication Foundation (WCF) service that must be installed on a website in Internet Information Services (IIS). 1. Run AX 2012 R3 Setup. 2. Select Microsoft Dynamics AX Components. 3. Select “I accept licence Terms” and click on Next button. 4. Click on Add or modify components. And click on next button. 5. In Add or Modify Component list. Select “Real time Service” under Commerce Data Exchange. And Click on Next button. 6. Setup will check prerequisite components for Real Time Service. (Note: – Make sure that there should not be any error). Once its Done , click on next button. 7. In Below Screen you have to configure below parameter. ( this is most IMP Steps) Application name – The name of the web application that hosts Real-time Service. Website name – The name of the website that hosts Real-time Service. App pool name – The name of the application pool that Real-time Service runs in. User name and Password – The credentials for the application pool identity. HTTPS port – The port on which Real-time Service receives secure HTTP requests. You can specify any available port. Verify that the port is open in Windows Firewall. TCP port – The port on which Real-time Service receives TCP requests. You can specify any available port. Verify that the port is open in Windows Firewall. SSL certificate thumbprint – The thumbprint for your Secure Sockets Layer (SSL) encryption certificate. You must obtain a valid, registered certificate from a provider. 8. Setup will re-validate the Prerequisite components as per configuration. Once it’s Done click on Next button. 9. Real time service is now ready to install. Click on Install button to start the installation. 10. Once Installation is done below screen will appear. 11. After this close all the window. And go services. In Services you can able to see Microsoft Dynamics AX Commerce Data Exchange : Real-time Service.