Introduction: This blog consists of information on adding notes section in to your form and the difficulties faced while adding the notes section. When to use notes on entity forms: Notes are quick, easy and create a time-stamp. You can use when temporary and not critical information need to be shared with others. Prerequisites: 1. Notes should be enabled on the entity. Open the entity in the solution and check the notes box. 2. If notes are not present on the form, add on the form. If the notes section is already present on the form, the notes button will be disable on the form. Note the below points before adding the notes section: Dynamics CRM allows only one Notes/Activities/Posts per entity and which is enabled by default. If you try to add one more notes, you will get the error message. It will be visible only for the Main forms, so if you are deleting the Notes/Activities/Posts from Main form, it will be visible on another main form. If you want to make use of Notes/Activities/Posts to be added on some other form. You can’t use a notes control for an entity that is not enabled for Notes, so unfortunately you cannot have just activities, or activity feed posts. Disadvantages: Notes are not searchable. Notes cannot be included in Reports or advanced finds. Notes do not roll-up. Users must re-create the same note several times for different records. Information may be lost.

One of the main reasons for the popularity of microsoft dynamics nav upgrade is its simple to learn interface and its adaptability. Microsoft Dynamics NAV is a famous ERP framework among fair size associations. It’s known for being anything but difficult to introduce and get familiar with its interface. It’s a crucial framework for most retailers as it controls your financials, flexible chain, deals, business insight and that’s only the tip of the iceberg.  As retailers develop however. the requirement for incorporating their NAV ERP gets apparent. Your ERP isn’t the main framework expected to run your activities. Retailers must have similar information between their POS, eCommerce, commercial center, 3PLs, and other significant frameworks. Coordinating Microsoft NAV with other retail frameworks is very difficult. Introduction: No. Series is used to create records in Dynamics NAV with unique numbers. Unique numbers are assigned to data records automatically using No. Series. The format to be used for the No. Series should be set up initially once which consists of a combination of numbers and alphabets. Pre-Requisite: Microsoft Dynamics NAV Purpose: In this article, I will be demonstrating the procedure to create a custom No. Series in a custom table. Procedure: Create a new field in Table 311 – Sales & Receivables Setup which will save the No. Series selected. Navigate to the properties of this field and in TableRelation property select Table 308 which is ‘No. Series’. Add the newly created field ‘CF_CreditNoteEntity’ to the Page 459 – Sales & Receivables Setup so that it is accessible to the user from the NAV windows or web client. Now create a new field ‘No. Series’ in a custom table with Data Type ‘Code’. Navigate to the properties of the No. Series field and in TableRelation property select Table 308 which is ‘No. Series’. Note: ‘No.’ field is the primary key of the custom table which will save the unique No. Series. Create two new variables in C/AL globals in the custom table. a. SalesSetup of DataType ‘Record’ and Subtype ‘Sales & Receivables Setup’ which is Table 311. b. NoSeriesMgt of DataType ‘Codeunit’ and Subtype ‘NoSeriesManagement’ which is Codeunit 396. In OnInsert() trigger of the table add the following code: In OnValidate() trigger of the primary key field which will save the unique No. Series add the following code. In this scenario, I have added it to the OnValidate() trigger of ‘No.’ Go to ‘No. Series’ which is Table 308 and create a new entry for the No. Series to be used. To generate ‘No. Series’ automatically you need to select ‘Default Nos.’ checkbox. If you also want the field to support manual nos. then you should select the checkbox ‘Manual Nos’. The ‘Last No. Used’ field gets updated automatically when a record is created and the unique No. Series is inserted in the table. Navigate to Sales & Receivables Setup which is Page 459 and select the No. Series for the newly created field in step 1 from the drop down list.                                                                                                                   Hence, automatically when you create a new record, the No. Series will get inserted and a unique record will be created. Conclusion: Thus following this procedure, a custom ‘No. Series’ can be created for a custom table with any combination of alphabets and numbers which will create unique records.

Introduction: In this blog we will discuss the different Power BI Premium Capacity nodes available and the steps to purchase these. We will also discuss how to assign a premium node to a workspace in Power BI. Power BI Capacity Based SKUs: There are 3 categories of SKUs that can be purchased which gives us a number of ways to embed our content using any of the capacities depending on our requirement. Following are the 3 different series provided by Microsoft. Power BI Embedded A SKUs This capacity is generally used by small ISVs for embedding own solutions. Unlike the other two series this series is charged on an hourly basis. It can be paused and started whenever needed and also it has additional scalability. Power BI Premium EM SKUs This capacity is also generally used by ISVs for 3rd party embedding in a custom application or in SaaS applications like Sharepoint or Teams. It offers everything provided by A SKUs and also offers the ability to share Power BI reports. EM SKUs unlike A SKUs cannot be paused and require a monthly or annual commitment. Power BI Premium P SKUs For this capacity, the hosting organization does not generally have any requirement for custom software development. It has all the features of E SKUs and also additional Power BI services like App sharing, Ad hoc dashboard sharing.etc. They allow the users to use Power BI’s browser based experience and are more dependent on the UI provided by Power BI. Purchasing the nodes: If you are a Billing Admin in your O365 tenant then you can purchase the capacity nodes under Purchase service in Billing. Currently the EM3, P1, P2 and P3 capacities can be purchased from the Office portal. The A series can be purchased from the Microsoft Azure Portal. Click on New and search for Power BI Embedded. Fill in the necessary details. A capacity administrator needs to be assigned, who will be responsible for creating the capacities and assigning it to the workspaces. Note: I still haven’t figured out where to find the EM1 and EM2 nodes but I’m presuming that they haven’t been released yet. Assigning a Capacity to a workspace: I am using the A1 node for this example. We can see that the Pause feature is available in this node. The first step is that the capacity admin logs into their Power BI account. It is important to note that the capacity admin should have a Pro License. Click on Settings and go to the Admin Portal. Next Select your capacity. Here we can manage capacity size, assign user permissions. etc. If you are opening the portal for the first time then there will be an Assign Workspace option available. Under User Permissions select Entire organization (Assign capacity to entire organization) or Specific users (Assign capacity to specific Users) Depending on the option selected above either the workspaces of the entire organization or the workspaces of the selected users will be loaded below Now we create a sample App workspace named ‘Test Workspace’ to which we will assign our capacity node. You can also use an existing workspace instead. Click on Workspaces and select Create app workspace Name your workspace and enter all the workspace members. Under the Advanced option there should be a Premium toggle button available(This option will only be available if the user is a Capacity Admin, Power BI Admin or a Global Admin and also the User permission mentioned above needs to be given). Turn the Premium option On. Click on Save. If you are using an existing workspace then go to workspace and click on the ellipses(…) beside the workspace and select the Edit Workspace option and enable the Premium option. To be sure that we have successfully backed our workspace with a capacity node, we can confirm by looking at the diamond icon beside our workspace name. Conclusion: We have successfully learnt how to purchase a Power BI capacity node and assign it to a workspace which will enjoy all the benefits provided by Power BI Premium and also give us Embedding Services with it.

Overview: With the new v9 release of Dynamics 365, a lot of user-friendly features have made life easier. Talking about the slick new Unified Interface! And if you want to make an App based on the same with components you need, it’s a hell lot easier too. New App with Unified Interface: You can either design an App in the Web Interface or in the new Unified Interface in v9 of Dynamics 365. Here’s how you can do it – Navigate to Settings > Apps. Then, click on create new App button as shown below. Now, you only get to choose either from the Web Interface or the new Unified Interface. So, it takes just a moment to get the interface ready for you to design.  Once prepared, you can start making your app, designing your site-map, dashboards, entities etc. For the sake of this blog, I’ve added a basic SiteMap, some Dashboards and a few Entities So typically, this is how I want my App to have! Once I have made all the changes, I’ll save and Publish the same. Accessing Unified Interface App: Once the App is published, it will appear in My Apps section as shown below: And I can then open and get the new Unified Interface. Now, you can work in the new Unified Interface with your custom app.

Introduction: To upgrade the database to NAV 2017, following steps must be completed. Convert the Database Upgrade the Application code Upgrade the Data For Converting the database, refer this link For Upgradation of the Application code, refer this link  This blog describes the steps to Upgrade the Data. Pre-requisites: A FOB file that contains the upgraded application code and upgrade toolkit. All application objects in the old database have been built. The database schema has been synchronized in the old application. All application objects are unlocked. All Microsoft Dynamics NAV Server instance records have been cleared from the dbo.Server Instance table in the old database in SQL Server. Updated permission sets permissions XML files. Windows Poweshell Sql Server Management Service(SSMS) Steps: The first seven steps are completed in the ‘Converting the database from NAV 2016 to NAV 2017’. SQL Backup Upload 2017 Licence Delete all objects from the old version database i.e NAV 2016 Uninstall NAV 2016 and install NAV 2017 Convert the NAV 2016 Database Connect to the server instance Run the Schema synchronization Importing the application objects: Import the all merged file (.fob) created in the upgrade of the application code. The system will prompt to open worksheet Click on Replace All then click on OK. Now import the upgrade code. This upgrade code is located in the NAV DVD in the Upgrade Toolkit folder NAV DVD > UpgradeToolkit >Data conversion Tool Import the Upgrade9001000.FOB file for upgrade from NAV 2016 to NAV 2017. Here 17 objects are imported. Run the Schema Synchronization: Open the Microsoft Dynamics NAV 2017 Development Environment, navigate to Tools menu then click on Sync. Schema For All Tables > With Validation. This will pop up a dialogue box, click on Yes. If Sync.Schema with validation pops up an errors like below ‘There is already an object named ‘CRONUS International Ltd.-$UPG Item Category’ in the database follow the below steps: Launch SSMS(SQL Server Management Studio), expand the Database converted Select the table and run the query to drop it Run the Data Upgrade Process Open the NAV 2017 Development Environment as Administrator. Navigate to Tools tab > Data Upgrade > Start. This will pop up a dialogue box, click on yes. Select the Execution mode as parallel, enable show progress and click on OK. If there are any errors you may get an error dialogue box. To view the error, Open Windows Powershell as Administrator, enter the below command Get-NAVDataUpgrade serverinstancename -Erroronly Get-NAVDataUpgrade Upgrade -Erroronly The above error is shown in the Codeunit 104075,compile the codeunit. The codeunit will pop up errors which needs to be fixed. Once the error is fixed compile all objects then run the Data upgrade process step no 10 This process will continue until all the errors are fixed. The data upgrade process is completed without any errors. Delete the upgraded objects After the upgrade is completed, delete the upgraded objects imported from the Upgrade Toolkit. Filter the upgrade objects by their version list. Select all the upgrade objects and click on Delete Set the Synchronization schema to Force and click on OK  After Deletion, compile all objects. Import upgraded permission set and permissions. Open the NAV 2017 Development Environment, open the NAV 2017 database ‘Demo Database (10-0). Navigate to XMLport 9171 Import/Export Permission Sets and click on Run Choose Export option and click on OK and save the file. Repeat the same procedure for XMLport 9172 Import/Export Permissions Now open the Upgraded database in NAV 2017, navigate to page 9802 Permission Sets and click on Run. Delete all permission sets except Super permission. Run XMLport 9171 to import permission sets, select the Import option then OK Select the permission sets exported  then click on OK. Run the Page 9802 Permission Sets, all the permission set are imported.  Repeat the same for XMLport 9172, import the permissions. Set the language of the upgraded database. Navigate to Tools select the language required then on OK. Add Control Add-ins Browse in the search bar to Control Add-ins to verify the below control Add-ins are present. Dynamics.Nav.Client.BussinessChart Dynamics.Nav.Client.PageReady Dynamics.Nav.Client.PingPong Dynamics.Nav.Client.VideoPlayer Dynamics.Nav.Client.SocialListener Import Payment Service and Data Encryption Key (optional). If we have used payment service in our old database then we need to re-set up payment service in NAV 2017 by importing the key. Browse to Payment service Connection set up in the search bar Click on Upload Key to upload the encrypted key. This key was downloaded in the previous version using the Download key.  To import key for Data Encryption Management, browse to Data Encryption Management in the search bar. Click on Enable Encryption to enable the encryption and import the key using Import Encryption Key. Before importing the key needs to be exported from NAV 2016. Conclusion : After the Upgradation of the Data, the upgradation of  NAV 2016 to NAV 2017 is successfully completed.  

Introduction: There are times when you may want to use Excel to view and interact with a dataset that you have Power BI for quick stretching of data slice and dice. Few people feel comfortable with excel PivotTable and PivotCharts, so by using Analyze in Excel, you can do just that, and access PivotTable, chart, and slicer features in Excel based on the dataset that exists in Power BI. Supported Version and Requirements: This feature support’s MS Excel 2010 SP1 and Later version. Excel PivotTables do not support drag-and-drop aggregation of numeric fields. Your dataset in Power BI must have pre-defined measures. Working: 1. Go to Power BI Workspaces and then go to datasets. When you select Analyze in Excel from the menu (…) associated with a dataset or report in Power BI, Power BI creates an .ODC file and downloads it from the browser to your computer. When you open the file in Excel, an empty PivotTable and Fields list appears with the tables, fields, and measures from the Power BI dataset. You can create PivotTables, charts, and analyze that dataset just as you would work with a local dataset in Excel. Dataset should have a pre-defined measures. The .ODC file has an MSOLAP connection string that connects to your dataset in Power BI. When you analyze or work with the data, Excel queries that dataset in Power BI and returns the results to Excel. If that dataset connects to a live data source using DirectQuery, Power BI queries the data source and returns the result to Excel. Analyze in Excel is very useful for datasets and reports that connect to Analysis Services Tabular or Multidimensional databases (because it provides a live connection to MSOLAP), or from Power BI Desktop files or Excel workbooks with data models that have model measures created using Data Analysis Expressions (DAX). 2. Open ODC file in Excel. Enable the security warning to access the dataset. Note: Administrators for Power BI tenants can use the Power BI Admin Portal to disable the use of Analyze in Excel with on-premises datasets housed in Analysis Services (AS) databases. When that option is disabled, Analyze in Excel is disabled for AS databases, but continues to be available for use with other datasets. This is additional feature that provide security feature to your dataset. Now that Excel has opened and you have an empty PivotTable, you’re ready to do all sorts of analysis with your Power BI dataset. Just as with other local workbooks, with Analyze with Excel you can create PivotTables, charts, add data from other sources, and so on. And of course, you can create different worksheets with all sorts of views into your data. Easy to Share: Once your workbook is saved, you can share it with other in your organization. When a user with whom you’ve shared your workbook opens the workbook, they’ll see your PivotTables and data as they appeared when the workbook was last saved, which may not be the latest version of the data. To get the latest data, users must use the Refresh button on the Data ribbon. And since the workbook is connecting to a dataset in Power BI, users attempting to refresh the workbook must sign into Power BI and install the Excel updates the first time they attempt to update using this method. Since users will need to refresh the dataset, and refresh for external connections is not supported in Excel Online, it’s recommended that users open the workbook in the desktop version of Excel on their computer.

Introduction: Messaging records management (MRM) helps organizations to manage email lifecycle and reduce legal risks associated with e-mail and other communications. MRM in exchange online is accomplished by using retention tags and policies. Retention Tags: Retention tags are used to apply retention settings to folders and individual items such as e-mail messages and voice mail. This specify how long a message remains in a mailbox and the action to be taken when the message reaches the specified retention age. When a message reaches its retention age, it’s moved to the user’s In-Place Archive or deleted. Types of Retention tags: Retention tags are classified into the following three types based on who can apply them and where in a mailbox they can be applied. Default policy tags – Applied automatically to entire mailbox. Retention policy tag – Applies automatically to a default folder. Personal tag – Manually to items and folders. Personal tags are available to Outlook web app users as a part of their retention policy. Creating retention tags: In EAC, go to Compliance center > Retention tags, and then click +. Retention tags are classified into three types, select one of the option. The New retention tag page title and options will vary depending on the type of tag you selected. Enter a name for tag, chose retention actions and period, click Save. Retention Actions: Delete and allow recovery – Allow the user to recover deleted items until the deleted items retention period for the mailbox has not reached. Move to archive – Move the message to user’s archive folder, this is applicable only for tags that are automatically applied to the entire mailbox (default) and applied by users to items & folders (Personal). Permanently delete – Purges the item from the mailbox database. Retention Policies: To apply one or more retention tags to a mailbox, you must add them to a retention policy and then apply the policy to mailboxes. A mailbox can’t have more than one retention policy. Retention tags can be linked to or unlinked from a retention policy at any time, and the changes automatically take effect for all mailboxes that have the policy applied. Creating a Retention Policy: In EAC, go to Compliance center > Retention policies, and then click +. In New Retention Policy, provide a name for the policy and click + to add retention tags. After click +, list of all the retention tags will shown and you can select from that. After linking retention tags to policy, click Save. A retention policy can contain the following tags: One DPT with the Move to Archive action One DPT with the Delete and Allow Recovery or Permanently Delete actions One DPT for voice mail messages with the Delete and Allow Recovery or Permanently Delete actions One RPT per default folder such as Inbox to delete items Any number of personal tags Default Retention Policy: Exchange Setup creates the retention policy Default MRM Policy. The Default MRM Policy is applied automatically to new mailboxes in Exchange Online. You can modify tags included in the Default MRM Policy. Place a mailbox on Retention Hold: Placing a mailbox on retention hold suspends the processing of a retention policy. Retention hold is designed for situations such as a user being on vacation or away temporarily. To set a mailbox on Retention Hold, you need to use Powershell. For placing a mailbox on Retention Hold: Command – Set-Mailbox “Uday Mane” -RetentionHoldEnabled $true To check whether the Retention Hold in enabled on a Mailbox: Command – Get-Mailbox “Uday Mane” | Select RetentionHoldEnabled To remove retention, hold from a mailbox: Command – Set-Mailbox “Uday Mane” -RetentionHoldEnabled $false Conclusion: So, this is how we can use MRM to manage email lifecycle and reduce legal risks associated with email and other communications.  

D365 Field Service Management stage furnishing venture organizations with instruments to smooth out their business forms – from ongoing portability over each significant gadget, to steering and work process computerization.  Make essential field administration assets, for example, item manuals, specialized help documentation, preparing, and related recordings promptly accessible to client care agents, accomplices, and field professionals.  Make work arranges straightforwardly from a case, client gateway, email, or legitimately from your CRM and track against SLAs, privileges, income and related expenses, and invoicing.  Consequently plan and allocate assets dependent on aptitudes, area, required parts, and the remaining task at hand. Courses are advanced to meet SLAs and limit drive times. CRM administration contracts assist you with keeping up guarantee and privilege data association-wide. Introduction: This blog explains how to show Resource Bookings as Calendar in D365 Field Service Portal. Steps of Implementation: 1.  Create a new Entity List in D365 Field Service for “Bookable Resource Booking” Entity as shown below 2.  Set Calendar View on Entity List as shown below 3.  Set Grid Configuration as shown below 4. After creating Web Page for Resource Booking ,Calendar will be shown as below Note: You can refer blog how to configure Web Page in D365 Online Portals by referring to this link. 5. Booking Details can be shown as below Conclusion: Above description in blog enables configuring Calendars in D365 Online Portals. Default Calendar View depends on the field value of “Initial View” in Settings header of Entity List below is view by Month setting.

Introduction: In this blog article, we will explain about the new Visual of Power BI: Ribbon chart! Ribbon Chart: The visual is like a stacked column chart, but each column’s inner categories are sorted according to their rank for that column. Additionally, the inner categories are connected by ribbons across the columns. Refer below Screen Captured: You’ll find this new chart option to the right of the combo chart. The chart’s field well and formatting options are the same as a stacked column chart with some extra formatting options for the ribbons. There’s a Ribbon card in the formatting pane that lets you control the ribbon style: Spacing between ribbons – You can use this option to set a gap width between the ribbons. By default, there is no spacing. Match series color for ribbons – By default, the colour of the ribbons is to match the category’s color, but you can turn this off and the ribbons will be grey in color. Transparency for ribbons – You can control the transparency of the ribbon’s color. By default, it is set to 30. Border for ribbons – By default, the ribbons don’t have a border, but you can turn borders on.  

Since integrating your ERP takes time and resources, you want to make sure the project is worth it before you dive in. There are many common signs that indicate that you need microsoft dynamics nav upgrade . Without integration, retailers rely on manually entering the same data into multiple systems. If you have teams or individuals solely dedicated to spending hours manually moving data, then you’re ready for automation. All these hours moving the data yourself could be better spent, like improving your customer experience. Relying on manual data entry is also more prone to human mistakes. All it takes is a typo in one system to offset your data. Bad data can lead to inconsistent product information across sales channels, inaccurate delivery addresses for online customers, and wrong inventory counts Introduction: Microsoft Dynamics NAV control add-ins can be created using the NAV .dll assembly viz. Microsoft.Dynamics.Framework.UI.Extensibility.dll assembly. This .dll binds the NAV control add-in and the NAV environment. This control add-in has to be implemented in Visual Studio and then registered in Dynamics NAV by navigating to Control Add-ins. Pre-Requisite: Microsoft Dynamics NAV Purpose: In this article, I will be demonstrating the steps to create and use a Client control add-in in Microsoft Dynamics NAV. Procedure: Open Visual Studio. Create a new C# class library project and add a reference to the Dynamics.Framework.UI.Extensibility.dllassembly. This assembly is present in the following directory: C:\Program Files (x86)\Microsoft Dynamics NAV\100\RoleTailored Client. In the Visual Studio project namespace, create a new interface and add code for the control add in. The code is mentioned below:[ControlAddInExport(“NAVaddin”)] The name ‘NAVaddin’ will be used while registering the control add-in in Dynamics NAV. Now you need to sign the assembly. Navigate to properties->Signing->select Sign the assembly. In the Choose a strong name key file drop down list, select ‘New’. In the Key File name enter an appropriate name and clear the ‘Protect my key file with a password’ check box. The next step is to generate a unique public key in Visual Studio for the project as this public key is required while registering the control add-in in Dynamics NAV. Navigate to Tools->External Tools. Parameters to be filled are as below: Title: Get &PublicKey Command: C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\sn.exe Arguments: Get &PublicKey Now, ‘Get PublicKey’ will appear as an option under Tools which on clicking will generate the public key for the project. After clicking ‘Get PublicKey’->the public key is generated and displayed as below: Save and Build the solution. After successful build of the project, the .dll file will be generated.   Creating the Resource .Zip File.You must create a single .zip file containing manifest and any of the resource files used in Visual Studio. This .zip file has to be used while registering the .dll in Dynamics NAV. The next step will be to copy the .dll file to two locations in Dynamics NAV as given below: C:\Program Files\Microsoft Dynamics NAV\100\Service\Add-ins C:\Program Files (x86)\Microsoft Dynamics NAV\100\RoleTailored Client\Add-ins Go to NAV administration and restart NAV services so that the changes are reflected. Navigate to ‘Control Add-ins’ in NAV windows client and create a new Control add-in. Add the same control add-in name which is mentioned is step 2: Click on ‘Import’ action to import the .zip file containing all the Visual studio resources as created in step 7. After performing these steps, the client control add-in will be registered in Dynamics NAV and the triggers defined in Visual Studio, if any will be visible in the NAV Development environment if the Control add-in is selected in the properties of the control. Conclusion: Using this procedure, you can create complex functionalities in Visual Studio and use the .dll control add-in file in Dynamics NAV. I have created SMS functionality from NAV and Digital Signature functionality in NAV using the above procedure of adding a client control add-in.