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.

Overview Spring 2017 update to Dynamics 365 is coming up in July 2017. And there are exciting new additions and improvements coming to Dynamics 365 For Sales. Here are the highlights on what’s up next – LinkedIn Sales Navigator: Improve performance of their sales processes from LinkedIn Company and Sales profiles Display Navigator person and company information on Lead, Account, Contact and Opportunity pages. Automatic daily updates between the two systems. Write select Sales Navigator activities (InMails, messages, notes and call logs) to D365 For Sales. D365 Connector for LinkedIn Lead Gen Forms (only if you use Lead Gen Forms for LinkedIn): Bring LinkedIn Leads to D365 Online using this connector. Automatically captures and syncs leads to further nurture them. Support for multiple LinkedIn member accounts. Configure how Leads will be captured. Analyze Lead performance. Prospect to Cash Integration: Connect D365 For Sales and D365 For Operations using Common Data Service. Maintain Accounts in Sales and sync to Operations as Customers. Sync Contacts Sync Products from D365 for Operations and sync them to Sales. Create Quotes in D365 for Sales and sync them to Operations. Generate Sales Orders in Sales for existing Productions and sync them to Operations. Generate Invoice in Operations and sync them to Sales. Relationship Analytics: Relationship health Most Contacted Relationship KPIs Dynamics 365 Administrator Role in Office 365: Assign D365 Admin role at a tenant level. Can manage instances and admin functions, access D365 application if they are licensed. Bulk Data Loader:  New cloud based service for bulk import/export to cloud staging tables and perform light data-quality functions. Then push back to Dynamics 365. Will be accessed from a link in Admin Center and will redirect of LCS. Cortana Integration: Surface relevant Activities, Accounts and Opportunities to Salespeople. Customer backup and restore (online only): Customer backup and restore on Azure servers securely. Database Level Encryption with Customer Managed Keys: Ability for customers to generate their own keys and upload it to Azure Key Vault. Also revoke access on demand in a self-service manner. Portal Features Ability to Include attachments on knowledge articles so that they can be displayed on the Portal. Improved Admin Wizard on Portal to add an entity to the Portal. When data is updated in the entity, it will be automatically available to Portal users who have access to these data. Source Code for Portals will be available on the Microsoft Download Center under MIT license for developers to download. This will let Portals be deployed for D365 Online as well as on-premise environments. Support Azure Ad-B2C for Portal authentication using a single sign-on configuration Configure portal authentication for SSO. Manage Portal security in Azure. Support Timezone independent date formats in Portal forms. This means that  

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.

Introduction: Sometime it happens that you want to write small piece of code and it should be accessible from outside but you may not have infrastructure ready for it. In that situation you can write a function which can be called from anywhere. Azure function provides required infrastructure for code you need to write and you can make it available within few minutes. You can use Azure functions where you code does not include any complex logic. Azure functions can be used for very small pieces of code which can be invoked via any triggered events. You can choose your language to write the code like C#, F#, Node.js, Python or PHP. Azure Functions lets you develop server less applications on Microsoft Azure. Description: 1. Features: Azure function provides the below features: Choice of language – We can write functions using C#, F#, Node.js, Python, PHP, batch, bash, or any executable. Pay-per-use pricing model – Pay only for the time spent running your code. Bring your own dependencies – we can include other library as well if needed. Integrated security – Protect HTTP-triggered functions with OAuth providers such as Azure Active Directory, Facebook, Google, Twitter, and Microsoft Account. Simplified integration – Easily leverage Azure services and software-as-a-service (SaaS) offerings. Flexible development – Code your functions right in the portal or set up continuous integration and deploy your code through GitHub, Visual Studio Team Services. 2. Function Task: Functions provides templates to get you started with key scenarios, Blob Trigger EventHubTrigger Generic webhook GitHub webhook HTTPTrigger QueueTrigger ServiceBusQueueTrigger ServiceBusTopicTrigger TimerTrigger Create your first function: Prerequisites: Windows Azure Subscription – you can also subscribe for a free trial of Windows Azure from URL. Add Function Apps In order to host your code, you must have a function app created in the Azure. Login to the azure portal and click on the +(plus) sign Select the function app and provide the required details Provide the Azure function details as shown below. Provide all the required field value and click create, you will able to see below screen, Create function: Click on the plus sign as shown Select the httptriger-csharp Provide a unique name to the function and click create Now you are read with the function that can be access from anywhere. This is the template you can write your own code, we will work with the sample code that generated automatically. Let’s test the function from outside. Copy the url form the console as show You will get the code url that can be called from any API tester application, lets we called it from the Postman application. As you can see in the below screen, I called the function from Postman and in out window you will find that it is showing message. It shows some validation message because I have not provided the required fields. I provided the name you will find that output shows the name with greeting. View the function logs Conclusion: So, it concludes that we can have small piece of code that can be called form outside and we don’t require to maintain the infrastructure.

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: While customizing or adding a button to ribbon there are chances that you want to add same behaviour as of an existing button. But it is not known how to check what logic has been applied to that button. Description: If you want a custom button to have same behavior as that of system button, then how to achieve this. This can be achieved by using the workbench Ribbon customization tool. Let’s see how to do that. Open Ribbon Workbench and select the solution which you want to customize. Here I want my custom button to have same behaviors as of the Qualify lead Right click on the Qualify button and select customize command. As soon as click on the customize button you will able to see all the customization that are applied on that button as show below. Now you can add all the display and enable rule to your command as shown below. Similarly, you can add display rule as show below. Now you have same customization as that of the lead button.  

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,