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,

As NAV 2017 introduced new features, they have added some fields in Sales & Receivable Setups. These fields are explained below : Following new fields are added in the Sales & Receivable setup as compared to NAV 2016. Default Item Quantity Create Item from Description Allow Document Deletion Before The functionality of these fields are explained below : Default Item Quantity : By default it will not be checked.  If the user checks it then, the default quantity in a sales line will automatically be set to 1 . (This will work only if the Type in the Sales Line is Item). Create Item from Description:  By default it will not be checked.  If the user checks it then, while entering Item description in Sales Line if the system is unable to find the same description in Item master, the system will prompt the user to create a New item or Select an Item From Existing List, as shown below. 3. Allow Document Deletion Before: If the date is provided in this field, system will allow to delete the document (Invoice & credit memo) only after checking the posting date which should be before the date provided in these field. This features might be very small but are very useful in day to day activities  by the user.

Introduction: In this blog, we will have a look on how the records can be retrieved from NetSuite on basis of a custom field value. Scenario: We had a client with requirement to integrate their NetSuite environment to CRM environment. The integration process from NetSuite basically triggers on the scheduled time set on the server scheduler. One of the entity that gets integrated is “Customer”. When Customer record is updated in NetSuite, a Boolean field known as “Dirty flag” is set as true in NetSuite. While integration the records retrieved are based on the Boolean field “Dirty flag”. Only the records which have Dirty flag as true are retrieved. The code that retrieves the updated records from NetSuite is as follows: The search is done based on a Boolean custom field. The search value for this field should be set as true. The above code is to search records from all the pages. The page size mentioned is 5 in the above code. Thus, each page will have maximum of 5 records on one page.  

In this blog, we shall see how can a user make simple modifications to the CRM Portal Entity Form using ‘Entity Form Metadata’. Pre-Requisites: D365 CRM Portals D365 CRM Environment Why Use Entity Form Metadata? Entity Form Metadata has a modification logic to arguments or has the ability to override the functionality of form fields which isn’t possible using the CRM’s native editing capabilities. Entity Form Metadata allows the user to configure specific pieces on the form like a sub-grid, the notes section or an entire Section or Tab on the form which cannot be modified at the top level configuration. Scenario: In the following scenario the user will see how to make simple customizations like converting a “Lookup” entity field to a “Dropdown” field  on the Create Case Entity Form on CRM Portals using Entity Form Metadata. In the following image below we see that the ‘Product’ field on the  Create Case  Entity Form which is a look up field which we will be converting to a dropdown field using ‘Entity Form Metadata’. Fig 1. Image of the Create Case Form before making changes using Entity Form Metadata Process: In order to make the above changes to the attributes that are present on the Entity Form in CRM Portals the user will have to create a Entity Form Metadata which will convert the lookup attribute to a dropdown list. Step 1: The user will have to go on the CRM Main Menu to Portals> Entity Forms> Customer Service-Create Case Form as shown below. Fig 2. Selecting the Create Case Entity Form Step 2: On the Entity Form the user will have to scroll down to the form till Entity Metadata property doesn’t appear. The user will have to create a new Entity Form Metadata by clicking on the ‘+’ option to the right as shown below. Fig 3. To create a new Entity Form Metadata Step 3: In the New Entity Form Metadata use will have to select ‘Type’ as ‘Attribute’ and select the Entity from the drop down list in ‘Attribute Logical Name’ to which the following change is to be made in this case we will select the ‘Product’ field. Under ‘Control Style’ select the Control Style as ‘Render Lookup as Dropdown’. Fig 4. Entering Specific Details into the Entity Form Metadata Dialogue Box. Step 4: Click on ‘Save and Close’ once the details is entered. Now open the Portal Form Page to which the changes are made. The user will find that the ‘Lookup’ Product field is converted to a ‘Dropdown’ field. Conclusion: Thus, in this way user can make simple customizations to the Entity Form Page in CRM Portals using ‘Entity Form Metadata’ which isn’t possible to be achieved at top level configuration methods.  

Introduction: Want to make a dedicated OneNote notebook per Dynamics 365 record? Dynamics 365 Integration is what you need. This integration provides you the ability to take notes in the notebook in context of Dynamics 365 record for selected entities. OneNote records can be directly accessed on the Activity wall of the record whether on web application or on the mobile apps. Pre-Requisites: Server based SharePoint integration needs to be enabled between D365 and SharePoint Online. OneNote integration is only supported for SharePoint Online. Document Management is enabled for the Entity and the same is setup in Document Management under Settings in Dynamics 365. Setting Up: Before we begin, look that OneNote Integration won’t appear yet in Document Management under Settings since we don’t have Server-based SharePoint Integration enabled yet. Once you’ve enabled Server-based SharePoint Integration, you’ll see OneNote Integration Note: By default, OneNote integration will be enabled for Account, Contact, Lead and Product. So, I’ll enable OneNote integration for one of my custom entities. Following are the steps to enable the same: I have an entity called Order Fulfilment. On this entity, I have the usual Activity Feed as below   First, the entity needs to be Document Management enabled to be able to be listed for OneNote Integration as shown in the image below on entity level. I’ll navigate to Settings > Document Management > OneNote Integration. Because Document Management has been enabled on Order Fulfilment entity, I can see Order Fulfilment (I’ve ticked the same and clicked on Finish)3. And DONE! Accessing OneNote for a record Once I’ve configured this, I’ll open the Order Fulfilment record I was looking at. Once I click on it, I’ll see a Notebook has been created. And clicking on the Untitled Notebook will take me to OneNote Online for that record Hope this was quick and easy!