Introduction: In this blog, we shall see how a user can install the ‘LinkedIn Sales Navigator’ on their MS D365 CRM online environment. Pre-Requisites: D365 CRM Online Environment MSDynamics 2016 and 365 Widget Rar File. Procedure: The following are the steps to Install the LinkedIn widget to Microsoft CRM D365 Step1: The user will have to download the zip folder from the following LinkedIn website link. Do not unzip the folder as we need to import the solution as it is to the D365 CRM Environment. For downloading the zip folder use the following link and save the zip folder to a particular folder. https://www.linkedin.com/help/sales-navigator/answer/78963 Click on the zip folder download link as shown in the above image. Step 2: Now the user will have to go D365 CRM and on the ribbon, go to Settings> Solutions as shown below On the solution page select ‘Import’ option Browse for the solution file that we had previously downloaded and click on ‘Open’ then ‘Next’ In the next window the user will get the information of the solution. The user can view the information by clicking on the ‘View solution package details’. Click on Next to proceed ahead. Note: User will have to check the ‘Enable any SDK message processing steps included in the solution’ if it is unchecked and click on the Import option A dialog box will pop up showing progress of the import. Once the importing has finished click ‘Next’. A summary window will display all the imported components, indicating the solution import. Step 3: The last step of the installation process is to assign all users a ‘LinkedIn Configuration’ security role to give them access to the integration. In the All Areas drop down, navigate to Settings > Security and click on Users. Select all the required users to whom you want to provide the LinkedIn widget access and click on ‘Manage Roles’ at the top. A dialog box will pop up as shown below and check ‘LinkedIn Configuration’ and click OK. The user has finished importing and configuring the LinkedIn for Microsoft Dynamics CRM online solution. Conclusion: Thus, we have seen how can a user successfully configure the ‘LinkedIn Sales Navigator’ widget for MS D365 CRM Online Environment.

Introduction: With themes in D365, organizations have the ability to uniquely brand the D365 System with supported way to apply organization’s logo and colour choices to the application. Themes: Themes in D365 can be incorporated in several simple steps, Step 1: Under Settings, select Customizations and then Themes. Step 2: By default, D365 default theme is present in the system. Now If we want to create theme for our organization, select New Theme. D365 default theme can be used as a reference to understand how themes work in D365. Step 3: Once New theme is selected the page layout is as follows: Let’s see how individual field works and what it means. Theme Name: Here user can specify the Theme Name. After a name is specified and record is saved then default values are set. Logo: Sets selected Logo replacing default Dynamics 365 logo. Click “New” in search option of Logo field. Logo Image recommended size is 400px in width and 50px in height also supported image file formats are .gif, .jpg and .png Enter details as required ,upload logo image and publish web resource. Click button in Ribbon “Publish Theme” and below are changes as highlighted. Logo Tooltip: Set Tooltip on Logo as highlighted below: Navigation Bar Color: Set Navigation Bar Color replacing default black Color. Navigation Bar Shelf Color: This field sets Navigation Bar Shelf Color of Navigation Bar Header Color: This setting sets Font Color of Header of Sub Area. Global Link Color: This field sets Color of link record. Selected Link Effect: This field sets Color of Selected Records. Process Control Color: This field changes Business Process Flow Header Color. Default Entity Color: This field sets default Entity Color for all Entities except Custom Entities. Default Custom Entity Color: This field sets default Color for all Custom Entities. Control Shade & Control Border: Above field settings set control border and shade. Step 4: Once theme is completed and we need to publish it by click Ribbon button “Publish Theme”. Note: Publish theme gets applied to all D365 users. Conclusion : Hoping this blog explains how to design theme for client.  

In this article, we are going to compare features of Microsoft Flow and Zapier. Real Time Integration: Microsoft Flow: Flow gets automatically triggered based on create/update/delete record defined in the workflow. Note: Triggers for Create, Delete and Update are available Zapier: Zap gets automatically triggered based on create record defined in the workflow. Note: Trigger for Create is available Scheduled Integration: Microsoft Flow: Flow can be scheduled by day, hour, minute, seconds. Recurrence action is used for the same. Zapier: Zap cannot be scheduled. It can only be triggered on Creation of new record. Triggers: Microsoft Flow: Triggers can be specified for any entity. Zapier: Triggers can be specified for limited entities. For example: For Dynamics CRM, the trigger can defined only for Contact, Opportunity, Lead and Account. Lookup Action: Microsoft Flow: Records can be looked up using GUID / Unique Identifier of the record. We can look up to any entity. Zapier: Lookup record i.e. Search in Zap is different for different Connections. Only few Entities is provisioned for Search Criteria for Search can be based on all fields or one field based on Connectors (Explained below with example) Search value can dynamic i.e. values can be retrieved through previous steps. For Example: Search for Salesforce can be based on any field For Dynamics CRM, condition for Search for Contact is based only on email address. Conditional Workflow: Microsoft Flow: Various flow control can be setup in Flow like if-else, switch-case, do-until, etc. Zapier: Logical conditions setup is currently not available in Zap. Filters: Microsoft Flow: Source records cannot be filtered. Zapier: Filter feature not available. Data Formatting: Microsoft Flow: Data fetched from Source cannot be formatted before sending to target. Flow supports simple one-to-one mappings. Zapier: Data fetched from Source cannot be formatted before sending to target. Zapier supports simple one-to-one mappings. Execution History: Microsoft Flow: Errors can be monitored in Activity section in Flow. Errors cannot be handled inside a Flow. Zapier: Errors can be monitored in Task History section in Zapier. Errors cannot be handled inside a Zap Debug: Microsoft Flow: Debug feature is not available for a Flow. Though, after execution you can get output of each step Zapier: Debug feature is not available for a Zap. Though, after execution you can get input and output of each step. Conclusion: Summary for the Integration Tools: Microsoft Flow vs Zapier. Features Microsoft Flow Zapier Real-Time Integration Yes Yes Scheduled Integration Yes No Execution History Yes Yes Error Handling No No Debug No Get output of each step after execution No Get output of each step after execution Triggers Create/Update/Delete Only for Create Lookup Action Immature Mature than Microsoft Flow Filters No No Conditional Workflow Yes No Data Formatting No No  

In this blog, we shall see how can a user can write a JavaScript Code and where exactly should the user place the code in order to customize the D365 CRM Portal for version 8.0+. Pre-Requisites: D365 CRM Portals D365 CRM Environment Scenario: The user is often confused as to where exactly should he write the Java Script Code to make the following customizations to the CRM Portals Web Page. We will write a simple JavaScript function to disable the fields in this case the user will disable the email and phone number input fields on the on the Contact Us Web Page of D365 CRM Portals as shown below. Fig 1: Image showing disabled email and phone number fields using custom JavaScript Process: Step 1: The user will have to go the CRM Main Menu to Portals> Web Pages and select the respective web page to which the user wants to implement the required changes as shown below. Fig2: Selecting the Web Page Step 2: On opening the Web Page the user will get a section called the Localized content. The user should select the option as shown below. Fig 3: Select the Localized Content Step 3: On selecting the option in the localized Content as shown in the previous step, the user will have to scroll down and expand the Advance tab where the user get two input sections which are ‘Custom JavaScript’ and ‘Custom CSS’ as shown below. The user has to put the custom JavaScript into the ‘Custom JavaScript’ input section. Fig 4: Writing the JavaScript into the ‘Custom JavaScript’ input section of the localized content Step 4: The user can also add the custom JavaScript Code to the front side editor of the Portal using the administrative tool as shown below. Fig 5: Writing the JavaScript Code on the Front End using administrative tool. Conclusion: Thus in this way we can implement a simple custom JavaScript Code to customize the D365 CRM Portal.

In today’s world of more informed and aware customers, the most effective way of meeting the ever-increasing demands of the customers is to go for Microsoft Dynamics CRM Sales Process. The process not only gives you a crystal clear understanding of the customer needs but also gives you insights to engage more effectively with them to meet up their expectations.  CloudFront has recently built up a Sales Methodology App for Dynamics 365 Sales for our Partner, Technical Sales Development (TSD). The App bolsters a perceived Sales Methodology which can assist you with expanding income and win-rate by appropriately qualifying and overseeing bargains, creating serious and partner techniques, making a monetarily stable offer, and arranging activities to settle the negotiation.  Introduction: In this blog, we will have a look on how a web service can be call from Plugin in Dynamics CRM. Steps to be followed: 1)     Create an entity “Product Configuration” which consists of 2 fields Key – Name of the Web Service Value – Web Service URL The basic purpose of this entity is to store the Web Service URL so that we don’t hard code the values in the code. Web Service URL- Where WorkOrder -> Controller Name and CreateWorkOrder -> Function Name 2)     Call the below function to call the Web Service. Retrieve Product Configuration function basically retrieves the record from CRM. private void CallWebService(IPluginExecutionContext context, ITracingService tracer, IOrganizationService service) { string licenseResposeJSON = string.Empty; ////// Retrieve Product Configuration details: URL tracer.Trace(“Retrieve Product Configuration details: URL”); string value = string.Empty; value = this.RetrieveProductConfiguration(service); tracer.Trace(“Downloading the target URI from Product Configuration: ” + value); if (value != string.Empty) { try { using (WebClientEx client = new WebClientEx()) { tracer.Trace(“Call Web Service”); client.Timeout = 60000; client.Headers.Add(HttpRequestHeader.ContentType, “application/json”); licenseResposeJSON = client.UploadString(value.ToString(), “1”); } tracer.Trace(licenseResposeJSON); context.OutputParameters[“WebServieCall”] = licenseResposeJSON; tracer.Trace(“Output Parameter is set: ” + licenseResposeJSON); } catch (WebException exception) { string str = string.Empty; if (exception.Response != null) { using (StreamReader reader = new StreamReader(exception.Response.GetResponseStream())) { str = reader.ReadToEnd(); } exception.Response.Close(); } if (exception.Status == WebExceptionStatus.Timeout) { throw new InvalidPluginExecutionException( “The timeout elapsed while attempting to issue the request.”, exception); } throw new InvalidPluginExecutionException(string.Format(CultureInfo.InvariantCulture, “A Web exception occurred while attempting to issue the request. {0}: {1}”, exception.Message, str), exception); } } } public class WebClientEx : WebClient { public int Timeout { get; set; } protected override WebRequest GetWebRequest(Uri address) { var request = base.GetWebRequest(address); request.Timeout = Timeout; return request; } } 3)  Web Service which calls Create WorkOrder function is given below: [HttpPost] public async Task CreateWorkOrder([FromBody]string value) { CRM_DataOperations operations = new CRM_DataOperations(); OperationResult result = await Task.Run(() => operations.CreateWorkOrder_Daily()); return Request.CreateResponse(HttpStatusCode.Created, “Message: ” + Enum.GetName(result.GetType(), result)); } Hope you find this helpful! Thank you.

In this blog article, I will explain about the new updates of Power BI related to Relative Date Slicer. In this introduce a new feature in date as Relative Date Slicer. In this update they previewing a relative date slicer, which lets you filter based on the last 1 or more years, months, weeks, or days. This makes date slicers much more powerful, as you can always filter your report to the latest data. We can choose the Relative option from the list of available date slicer types. Once you select relative from the list, you will be able to specify the date to filter by. We have following seven options to display data: Days Weeks Weeks (Calendar) Months Months (Calendar) Years Years (Calendar) If you pick an option marked with (Calendar), the filter will be based on calendar periods. For example, if you filter to 2 years, data from the last 2 years from today’s date will show. If you filter 2 years (Calendar), data from the last 2 completed calendar years will show. We show the dates used for filtering under the slicer, so you always know what data you are looking at. You can also switch to filter to this period or the next period. By default, the date range includes current date i.e. today’s date, but we can override this in the formatting pane for the visual: This is useful if your data hasn’t refreshed today and you don’t want to include data from incomplete days. Turn on this feature through File > Options and settings > Options > Preview Features > Relative date slicer.

Microsoft Dynamics Nav integration is a default integration setup for Dynamics Nav that gives an option to integrate and use Microsoft Dynamics CRM entities with itself. The only thing that needs to be done for the integration is to enable the default integration setup after which you are good to go. After the successful integration, the user is able to integrate accounts, contacts, products, user, transaction currency, Sales Order which are synchronise data of Microsoft Dynamics CRM with the customers, contacts, items, Salesperson, Currency, Sales Order and Unit of measure which are the entities of Microsoft Dynamics Nav. This integration or linking of the records eases the process on many levels giving the customer a hassle free transaction and complex free system Introduction: Single sign-on (SSO) in Dynamics NAV is a process which authenticates a user to access NAV Web client and NAV windows client using Office 365 email login credentials. When a new Office 365 subscription is provisioned, the Azure AD tenant for this subscription has to be created. Pre-Requisites Microsoft Azure Active Directory Module for Windows PowerShell Microsoft Online Services Sign-in Assistant You can download the setup of Microsoft Online Services Sign-in Assistant from here Microsoft Dynamics NAV 2017 Purpose In this article, I will be explaining the procedure to configure Single Sign-on in Dynamics NAV with the Office 365 login credentials of a user using Windows PowerShell. Procedure: Go to Microsoft Dynamics NAV 2017 Administration and in the NAV instance enter the Certificate Thumbprint (the certificate can be either an SSL certificate or a self-signed certificate) Save the changes and restart your NAV instance. Go to mmc.exe and navigate to the certificate that is being used for Single sign-on. In mmc.exe, in Personal certificates section, in ‘Manage private keys’, add ‘NETWORK SERVICE’ as a user name and grant full control permissions to ‘NETWORK SERVICE’ user. In mmc.exe, along with Personal certificates section make sure the certificate is present in trusted root certification, Enterprise trust, Trusted publishers and Trusted people. Navigate to the user for which Single sign-on is being set up in NAV and under Office 365 Authentication enter the Office 365 email of the user.  Now run Microsoft Azure Active Directory Module for Windows PowerShell as administrator. Navigate to the Service folder to find NavAdminTool.ps1  module and run the following command in PowerShell to import the module Import-Module “C:\Program Files\Microsoft Dynamics NAV\100\Service\NavAdminTool.ps1” Navigate to the RoleTailoredClient folder to find ps1 module and run the following command in PowerShell to import the module. Import-Module “C:\Program Files (x86)\Microsoft Dynamics NAV\100\RoleTailored Client\NavModelTools.ps1” To import NAVOffice365Administration Module, navigate to the Microsoft Dynamics NAV DVD and then to NAVOffice365Administration. Run the following command in PowerShell to import NAVOffice365Administration.psm1. Import-Module “C:\Users\iotapadmin\Documents\CU 5 NAV 2017 W1\NAV.10.0.16177.W1.DVD\WindowsPowerShellScripts\NAVOffice365Administration\NAVOffice365Administration.psm1” To configure your Microsoft Dynamics NAV Server for single sign-on, you have to run the cmdlet  Set-NavSingleSignOnWithOffice365 in PowerShell with the following parameter set: Set-NavSingleSignOnWithOffice365 -AuthenticationEmail “YourAuthenticationEmail” -NavServerInstance “YourNAVServerInstance” -NavUser “YourNavUser” -NavWebAddress “YourNavWebClientAddress” -NavServerCertificateThumbprint “YourNAVServerCertificateThumbprint” -NavWebServerInstanceName “YourNavWebServerInstanceName” After entering this command a pop up box shown as below appears with the Office 365 email ID given in the above command and you have to enter the password of the given Office 365 email ID: After entering the password, the below output will appear in PowerShell: Copy and save the URL that appears at the end in PowerShell as it will be required later. Navigate to the ClientUserSettings file of the user and change the following parameters:Change ClientServicesCredentialType parameter value from ‘Windows’ to ‘AccessControlService’. Change the ACSUri parameter value to the value of URL link generated after the PowerShell command runs which I have mentioned in step 8. The parameters of the web client web.config file have not to be modified manually. It is automatically modified after the PowerShell command script runs. After SSO is configured, when you start Dynamics NAV Windows client and Web client, you have to enter the credentials of the Office 365 email ID which is provided while running PowerShell script in step 8. Fig: Windows Client Fig: Web Client

Introduction: Info code is used to capture additional information and Point of Sales. It Prompt Point of sales User to enter information at time various action on Point of Sales. This various can be like, Sales transaction, Return, payment method, customer. In this blog we demonstrate info code setup on Sales return Product. Scenario: Customer want to return some product, company want to know why customer is returning the Product and want to capture reason in Point of sales. Follow the below steps to configure info code setup return transaction. Step 1: Open then Dynamics 365, go to the retail and commerce Go to Channel Setup and click on info code. Step 2: Click on New Button. In Info code Number mention “Sales_Ret” , In description write “Sales Return Info code”. Prompt text will display on Point of Sales. In Put type Select Option Text. It Mean Point of Sales User will enter the reason in text format. In General Tab Select Yes in Input required Step 3 : Go to POS Profile and select Functionality Profile Select functionality Profile of store which you want to change. Step 4: Click on Edit button and go to Info Code Tab. In Info code tab Click on Return Transaction and Select “Sales_Ret”.Click on Save button. Step 5 : go to Channel Database and run the Job for that store. After that login in MPOS Or CPOS and Post return sales Entry. POS will POP-UP with Return Info code. From above steps with you can assign info code entry to POS Transaction.

Introduction: This blog explains how to define relationship between Entities in Scribe Connector CDK. Problem Statement: We often get requirement from Client to define relationships between entities in custom Scribe Connector Solution: Below is code snippet which explains how to define relationship between Customer and Contact. Step 1: Define child enity (Contact) Object definintion and add to objectDefinitions Step 2: Define parent enity (Customer) Object definintion Step 3: Define relationship between entites, points to remember as below: ThisObjectDefinitionFullName property set parent entity name RelatedObjectDefinitionFullName property set child entity name RelationshipType property set direction as “RelationshipType.Child” ThisProperties & RelatedProperties property should be same in both Parent and child entity. Step 4: Add relationship to parent entity(Customer) and add parent entity(customer) to objectDefinitions. Conclusion: Hope above scenario of defining relationship between entities help in real scenario of development.  

This is an awesome feature, which helps to capture the signature on mobile and tablet devices. Display the signature on the report: We can create report which will display an image captured by Pen control. Before moving towards the solution, mentioned below are the steps to setup the environment/Pen control. We added one multi-line text field on order form and configured it to use a Pen Control on phone and tablet app. Data stored in base64 value: When we draw something using pen control on tablet and mobile device, it is stored in the background, in encoded characters in the same multiline text field, as shown below. “data:image/png;base64,iVBDLSJDFASSKSDLKSLKNSLD/SDFSF…” In order to show the actual image/signature in the report, we just need to perform a nifty trick. Add that multi-line text field in your dataset. Insert image control and setup image properties as shown below. Image Source: Select “Database”. Use this field: add expression as follow, “IIF(NOT IsNothing(Fields!new_customersignature.Value),Fields!new_customersignature.Value.ToString().Split(“,”).GetValue(1),””)” **** Here we are just taking the encoded characters by splitting the field by comma “,”. We are excluding “data:image/png;base64,”. Use this MIME type: Select “image/x-png”. This setting results in pen control image in the report,