Introduction: With the help of XML port, it is possible to import and export data in Dynamics NAV. While exporting data to an Excel sheet, we always have a requirement to export data along with the column captions to an excel sheet. In this blog article, I will be explaining the procedure to achieve the same. Pre-requisite: Microsoft Dynamics NAV 2017 Procedure: Enter a node name. I have entered my node name as ‘Root’ with Node Type as ‘Element’ and Source Type as ‘Text’. For the caption names, first create a node with Node Type as ‘Element’ and Source Type as ‘Table’. Enter the Data Source as ‘Integer’ which is a virtual table in Dynamics NAV. Now enter a node name for your first caption name. In this example, I have entered ‘VINTitle’ as my first column caption name with Node Type as ‘Element’ and Source Type as ‘Text’. Go to C/AL code of ‘VINTitle’ which is my first node name and in ‘OnBeforePassVariable()’ write the code for the caption name that should appear in the Excel sheet when data is exported.This will display the name of the field which is entered in the table or you can also manually assign the name of the caption that should appear in the Excel sheet after exporting data as shown below. After the caption name is mentioned, now you have to enter the value which should be fetched from the table and appear in the Excel sheet. Enter the node name for your table with ‘Node Type’ as ‘Element’ and Source Type as ‘Table’. Enter your Data source. In this I have taken ‘Item’ as my Data source and the field ‘No.’ of Item table. Conclusion: After exporting data to an Excel sheet, the column captions appear in it along with the values of the column.  

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: There can be requirements to delete the components from the managed solution. Neither directly deleting the components from managed solution works nor deleting the field from unmanaged solution and migrating as managed solution to target environment works. We can make use of OOB feature of solution management. OOB feature used is Clone the solution. The version of the solution will be upgraded when we clone the solution. Steps: Steps to be followed are given below: Delete the components from your unmanaged solution that are not required or replaced. Make note of Version Number and click on Clone Solution. You can check the Version Number. It is increased by 1 count. Click on Save Version of the unmanaged solution will be changed Export the solution as managed and import on the target environment While importing this solution, make sure that you checked “Stage for Upgrade” When solution import completes, you can see “Apply Solution Upgrade” option. After applying solution upgrade, two difference can be seen in already installed managed solution on target environment. Version changed to 1.1.0.0 The component deleted in unmanaged solution will also be deleted in managed solution Conclusion: Thus, managed components can be deleted using OOB feature.

Introduction: This article focuses on how to create a Role center page and assign the role to a user as a user profile. The requirement was such that the user needs a Role center for the HR where the HR can view the Active, Inactive and Terminated employees and can also view the List of employees, Leave application list etc. Pre-requisites: Microsoft Dynamics NAV 2017 Steps: 1. Create a query with Data Source as Employee Table, create a filter field Status, here status is a option field which has three options -Active, Inative and Terminated.Create a column field and set Method type as Totals  and Method as Count. 2. Create a table with name e.g. HR Cue table. Here set the fields FieldClass to Flowfield and CalcFormula to Count. 3. Create a global function CountOrders and define the query in the variables. Here in the function, depending on the field number selected, it calls the query and sets the status to it. 4. To display Cues on the Role centre, we need to create a Page with Group subtype as CueGroup. 5. Use CueSetup codeunit for setting up cues and create an action Setup Cues. Create a local function CalculateCueFieldValues which checks if the field is active then it calls the global function CountOrders of HR Cue Page. 6. Create a Control Action as New Employee and set RunPageMode to Create and Run Object to Page Employee card. On running the cue Page 7. Create a new page for the Role Center with container subtype RoleCenterArea. 8. In Action Container subtype create HomeItems and add Action List. 9. In the Windows client, create a new Profile HR 10. Browse to the User personalization in the search bar in windows client , select the user HR and assign the HR Profile to it. 11. Log in to the Windows client/Web client.  

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.  

Introduction: Many of client required report with dynamics Column in Navision. We all know dynamics data is displaying top to bottom. But what happen if customer want data left to right. And As data increase Column also increase in the report. In this blog, I will show you Item inventory report, where Item will display in row and location will display in Column. But when you add any new location in Navision and Post any Item Journal, sales, purchase  entry for that location, that new location will added in report Column. Steps 1: Open Navision Development Environment. Go to Object Designer.  And Create New Reports. For Demo I created New Report “ Item By Location New “ report ID 50029. Steps 2: GO to Design mode of that report. Take Item table in Data Item and Item Ledger Entry table in 2nd data Item. Relation set DataItemLink “Item No.=FIELD(No.)” in Item Ledger entry Property. Select the Column from the table. For the demo, I have taken only 4 fields, you can as fields as you’re your requirements. Steps 3: Go to view and and select Layout option. Here I am using SSRS Report Builder. Click on Insert , then click on Table button and select Table  Wizard Option. And select 1st option as per screen shots. Step 4: In Column groups click and drag Location code , for Row Group Item No. and in Value Sum of Quantity. Click on next and finish. Steps 5: Now add Item description fields on right side of Item. Step 6: Save the report and run. Click on preview. Steps 7 : Create new location and post Positive adjustment entry for that New location and again preview the report. New location is added in that report and its inventory Update. Conclusion :- With this method you can create dynamics column reports, which can be print left to right column.  

Introduction: This article focuses on how to restrict other users and allow only a particular user to user a specified action button in a Page in NAV 2017. The requirement was such that the page Purchase quote is to be signed off by the CEO and then Purchase order is created. Here, an action button is created called Sign off, where on click of the button, the boolean field called Sign off which is an un-editable field is enabled. Only the CEO should have the access to Sign off the Purchase Quote. The other users should be restricted from signing off the Purchase Quote Pre-requisites: Microsoft Dynamics NAV 2017 Steps: 1. In the NAV Development Environment, create a Boolean field. e.g CEO in the User Setup table. 2. Add this field to the User setup page and enable this field for the CEO user. 3. Create a button Sign off in the purchase quote. Create a new codeunit and subscribe it to the action button Sign off. 4. Create a global variable User Setup in the codeunit and refer the below code. 5. In the Windows client/Web Client, browse to Purchase Quote from the search bar. 6. Edit any Purchase Quote and click on Sign off. Here if the User is not the CEO, in the above image the user is OETIADMIN ,a message is displayed ‘Only the CEO can Sign off this purchase document’ 7. If the User is the authorize user to sign off in this case the CEO then the message is displayed as Purchase Quote is signed off.

In this blog article, we will see how we can override Form Data source method using Extensions in Dynamics 365 Operations. Now as recommended by Microsoft we must avoid Overlayering and instead use Extension. For extension, we have to use pre or post event handlers methods. In this blog we will create event handler of OnActivated() method of SalesLine DataSource of form SalesTable. Create a new Class: class CFSActivateButton {    } Copy and paste OnActivated() event handler of SalesTable DataSource in Class:   /// <summary> /// To activate or deactivate Create Service Order button based on CFSProjId field of SalesLine /// </summary> /// <param name=”sender”></param> /// <param name=”e”></param> [FormDataSourceEventHandler(formDataSourceStr(SalesTable, SalesLine), FormDataSourceEventType::Activated)] public static void SalesLine_OnActivated(FormDataSource sender, FormDataSourceEventArgs e) {              FormDataSource      fds = sender.formRun().dataSource(“SalesLine”);         SalesLine           salesline = fds.cursor();         FormRun             fr = sender.formRun();         FormControl         fc = fr.design(0).controlName(“CreateServiceOrder”);                if(salesLine.ProjID)         {             fc.enabled(true);         }         else         {             fc.enabled(false);         }     }  

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  

What is XRM toolbox? XrmToolBox is a Windows application that connects to Microsoft Dynamics CRM, providing tools to ease customization and configuration tasks. It is shipped with more than 30 plugins to make administration, customization or configuration tasks easier and less time consuming. XRMToolBox is free of cost, but you can donate to support development. In this blog, I will list down the top 5 tools from XRM toolbox for both developers and CRM Administrators. How to Use it? Documentation is available through the wiki of XrmToolBox Github’s repository. You will find information about prerequisites, a list of known existing plugins, help on how to connect to your Microsoft Dynamics CRM deployment, and much much more.. Top Tools of XRM toolbox for Developers. 1.  WebResources Manager Author- MscrmTools Description – Manage your webresources easily. This tool has saved me hours of time for creating, updating and managing the web resources for Dynamics CRM. This is a must have for all the Developers 2.  SiteMap Editor Author – MscrmTools Description – Manage the SiteMap with no XML edition. Editing Sitemap XML is scary for any developer as any mistake in XML can make the Entire CRM unusable. This tool helps to edit your sitemap components. You can easily create areas and subareas, update the order and copy/ paste components from one area to another. You can also update all the sub area details like icon, titles for multiple languages etc. 3.   Ribbon Workbench 2016 Author – Scott Durow Description – Edit the Dynamics CRM Ribbon or Command Bar from inside the XrmToolbox. By installing the Ribbon Workbench you’ll quickly be performing customisations that were previously only possible by time consuming and error-prone manual editing of RibbonDiff Xml. Learn More – https://www.develop1.net/public/rwb/ribbonworkbench.aspx 4.  FetchXML Builder Author – Jonas Rapp Description – The tool will assist in three major areas: Constructing FetchXML in ways that Advanced Find cannot – aggregates – outer joins – “has no”-queries – attributes from multi-level linked entities Querying CRM for information not (easily) found in the CRM UI – system / internal entities – attributes hidden in CRM UI – join on other fields than relationships Developer assistance – Generate C# QueryExpression code from fetch xml – Generate OData query string from fetch xml – Easy to use UI to compose queries for reports in CRM The tool reads metadata from CRM to assist with selecting entities, attributes, relations and to perform validation of condition values. To make it more appealing, there is also the possibility to have it show “Friendly names”, which will replace the technical names of entities and attributes with their display names in the users’ currently selected language, much like Advanced Find does. 5.  Metadata Document Generator Author – MscrmTools Description – A tool to generate excel and word document with entities and attributes information. You’ll no longer have to write “by hand” these awful tables full of metadata information. Top Tools of XRM toolbox for Developers: 1.  Your User Security – Magnified Author – NORRIQ Belgium Description – Provides a detailed overview of a specified System User’s security. Very helpful to identify the exact permission a user has on entity based on all the roles assigned to him 2.  Form related tools Author – MscrmTools Description – Set of tools for XrmToolBox regarding form management4 3.  Solution Components Mover Author – MscrmTools Description – Transfer solution components across solutions. Again a big time saver for moving components from one solution to another. 4.  User Settings and Utility Author – MscrmTools Description – Manage and update All user’s personal settings in Bulk 5.  Attribute Usage Inspector Author – MscrmTools Description – Inspects the usage of attributes per entity. Admins can review which attributes are not used across all entities and which are used most.