Introduction: Across your organization, you probably have different types of content that require different actions taken on them to comply with industry regulations and internal policies. Labels in Office 365 can help you take the right actions on the right content. With labels, you can classify data across your organization for governance, and enforce retention rules based on that classification. With labels, you can: Enable people in your organization to apply a label manuallyto content in Outlook, OneDrive, SharePoint, and Office 365 groups. Users often know what type of content they’re working with, so they can classify it and have the proper policy applied. Apply labels to content automatically if it matches specific conditions, such as when the content contains: Specific types of sensitive information. This is available for content in SharePoint and OneDrive. Specific keywords that match a query you create. This is available for content in Exchange, SharePoint, OneDrive, and Office 365 groups. The ability to apply labels to content automatically is important because: You don’t need to train your users on all your classifications. You don’t need to rely on users to classify all content correctly. Users no longer need to know about data governance policies – they can instead focus on their work. Note that auto-apply labels require an Office 365 Enterprise E5 subscription. You create and manage labels on the Labels page in the Office 365 Security & Compliance Center. Create a Label. Sign in to Office 365. In Office 365 Admin Center, go to Admin Centers > Security & Compliance. In Security & Compliance, go to Classifications > Labels. Click on Create a label. Provide a name for Label and description. In Label settings, there is Retention option apart from Retention policy. You can turn this on if you want to apply retention settings to that label and if not, you can simply click on Next. If you turn this On, a various parameter will be shown (as shown in below image). Retain the content – Select the retention period that for how the data will be preserved. What do you want to do after this time – Here we need to select the action which will be taken after the retention age has reached. Label classification – If this is selected, users won’t be able to edit or delete the content or change or remove the label. After providing Label settings, click Next. Review your settings and click on Create this label. Publish labels in Office 365. The primary purpose of the label policy is to group a set of labels and specify the locations where you want those labels to appear. Sign in to Office 365. In O365 Admin Center, go to Admin Centers > Security & Compliance > Classification > Label Policies. Click Publish labels and choose the labels you want to publish for this label policy. A single label can be published in many policies. After adding label, you need to choose the location where you want to publish these labels. Name your policy. Review your settings. Click on Publish labels, it will take up to 1 day to publish these labels in the location you chose, so after clicking on Publish labels you will see the below screen. As it takes normally 1 day to publish the status will be in Pending till then. Applying Labels to the documents in SharePoint and OneDrive. From Office 365 Home tab, click the SharePoint tile. On the new SharePoint tab in your browser, click a site that needs an O365 label assigned. You can assign label to the whole document library at once or you can select the document for which you want to assign label. Applying label to individual document, select the document and apply label. Applying label to a document library, select that Document library > Library settings > Apply label to items in this list or library. Click on Apply label to items in this list or library and select the label you want to apply. Similarly, you can also apply labels to OneDrive document. Conclusion: This is how we can create Label and Label policy, then publish it so that users can classify data across organization for governance and enforce retention rule based on the classification.

Microsoft SQL Server Analysis Services is a server-based solution  that provides online analytical processing (OLAP) functionality. Analytical reports help users examine business data and identify trends that they might not otherwise discover when viewing data on traditional reports. To integrate Microsoft Dynamics AX and Analysis Services, you must perform the following steps: Step 1: Complete the prerequisite tasks: Verify that you have the permissions that are required to configure Analysis Services. Create a domain account to run the Analysis Services service. Assign the .NET Business Connector proxy account to the server administrator role in Analysis Services. Install prerequisites. Step 2: Configure Microsoft SQL Server Analysis Services: Start Microsoft Dynamics AX Setup. Under Install, select Microsoft Dynamics AX components. On the Select components page: Select the Analysis Services configuration check box. Click Next. On the Prerequisite Validation page, resolve any errors. When no errors remain, click Next. On the Select a file location page, select the location, and then click Next. On the Specify a location for configuration settings page, specify whether you want the cubes to access configuration information from the registry on the local computer or from a shared configuration file. If you select to use a shared configuration file, you must enter the network location of the file. Click Next. On the Connect to an AOS instance page, enter the name of the computer that is running the Application Object Server (AOS) instance On the Specify Business Connector proxy account information page, enter the password for the proxy account that is used by Business Connector. Click Next. On the Specify an Analysis Services instance page, select an instance of Analysis Services. Click Next. On the Connect to a SQL Server Database page, follow these steps: Select the computer that hosts your Microsoft Dynamics AX online transaction processing (OLTP) database. Select the Microsoft Dynamics AX OLTP database. Click Next. On the Ready to install page, click Install. Click Finish to close the Setup wizard. Step 3: Complete the Analysis Services integration: Install SQL Server Shared Management Objects on Microsoft Dynamics AX client computers. Verify that information about exchange rates has been entered. Click System administration> Setup > Business intelligence > Analysis Services > System currency and exchange rate type. Set up OLAP Administration Form Click System administration> Setup > Business intelligence > Analysis Services >Analysis Server Deploy the default cubes that are included with Microsoft Dynamics AX. PS: Ensure that the Microsoft Analysis Server should be connected to the Microsoft SQL Server Management Studio for the respective Server along with correct logon Credentials. Open the Microsoft Dynamics AX client. Click File > Tools > Business Intelligence (BI) tools > SQL Server Analysis Services project wizard. On the Analysis Services project wizard page, click Next. On the Select an option page, click Deploy, and then click Next. On the Select an existing Analysis Services project page, click Select a project from the AOT. Select the project you want to deploy from the list, and then click Next On the Deploying page, click Next when the deployment is completed. Click Finish to close the wizard. Configure the cubes, based on the changes that you have made to the Microsoft Dynamics AX configuration or license keys. Click Tools> Business Intelligence (BI) tools > SQL Server Analysis Services project wizard. Click Next. On the Select an option page, select Configure. Click Next. On the Select an existing Analysis Services project page, select the project to update. You can select a project from the AOT or from disk. Click Next After the project builds, click Next Select the Apply the Microsoft Dynamics AX configuration to the Analysis Services project check box. Click Next. Select additional languages for which to provide label translations and then click Next. To Run the Report: Click on Accounts Payable>Reports>Statistics>Vendor>Top Vendors by YTD Purchase  

Introduction: In this blog, we will be demonstrating how to use JavaScript to check user security roles. This is applicable in organization where, there are users with multiple security roles. And only users with a specific role assigned to them should be allowed to carry on certain tasks. Scenario: There is an organization with two users,”User A” is assigned a custom role and “User B” is not assigned a custom role. Only “User A” should be able to Save the form as he/she has the custom role. Implementation: Step 1: Create two users “User A” and “User B”. Step 2:   Create a custom security role “CustomRoleA”. “User A” has the following security roles: Salesperson Sales App Access CustomRoleA “User B” has the following security roles: Salesperson Sales App Access Step 3: Now we write a JavaScript code to check the logged in users security roles and accordingly allow only that user to save the record who has the “CustomRoleA” security role. If a user without that security role tries to save the a newly created record, an error notification is shown and record is not saved. Step 4: Save this as a new JavaScript web resource in Dynamics 365 and we will make this code run on the “Contact” form which will be triggered on the form onSave event. Step 5: Now when “User B” makes a new record and tries to save it the following error message is shown. The record can’t be saved. The search results as shown in the below image states that there is no such record. Step 6:  When “User A” tries to make a new contact and save, the permission is granted to save the record and in the search the record is shown as shown in the below two images. Conclusion: By checking the security roles different functionalities can be restricted for any user like show/hide fields or buttons.

Introduction: In this blog article, we will discuss working of Media controls in Power Apps Media Controls: There are 7 Media controls in Power Apps Image Camera Barcode Audio Video Microphone Add Picture Image Control: Shows an image from, for example, a local file or a data source. Description: If you add one or more Image controls to your app, you can show individual images that aren’t part of a data set, or you can incorporate images from records in data sources. Example: Show an image from a local file Steps: 1. On the Content tab, click or tap Media, and then click or tap Browse. 2. Click or tap the image file that you want to add, click or tap Open, and then press Esc to return to the default workspace. 3.  Add an Image control, and set its Items property to the name of the file that you added. Output: Camera Control: A control with which the user can take photos by using the camera on the device. Description: If you add this control, the user can update a data source with one or more photos from wherever the app is running. Example: Add photos to an Image gallery control Steps: 1.Add camera control set it’s OnSelect Property to Collect(MyPix,Camera1.photo). (here Camera1 is the name of camera control.) 2. Add gallery control set its item property to MyPix.Url 3. Set the Image property of the Image control in the gallery to ThisItem.Url. Output: Barcode Control: A control with which the user can take photos by using the barcode scanner on the device. Description: If you add this control, the user can update a data source with one or more photos from wherever the app is running. Steps: 1. Add a barcode control. 2. Add a label control and set its Text property to (here Barcode1 is the name of barcode control) Output: Microphone control: A control with which the user can record sounds. Description: If you add this control, the user can update a data source with one or more sounds from wherever the app is running. Steps: 1. Add Microphone control and set its onStop Property to Collect(MySounds,MyMic.Audio). (here MyMic is the name of microphone) 2. Add a blank gallery control and set its items property to MySounds and add audio control inside it. And set its Media Property to ThisItem.Url 3. Add A button if you want to remove any audio. Set its OnSelect property to : Remove(MySounds,ThisItem) Output: Add picture control: Takes a photo or loads images from the local device. Description: With this control users can take photos or upload image files from their device and update the data source with this content. Example: Add images to an image gallery control Steps: 1.Add an Add Picture control 2. Add Button control inside Add picture control. 3. Set OnSelect Property of button to: Collect(Pics, AddMediaButton2.Media) 4. Add gallery control and set its items property to pics. (gallery control will display all the images which are added) Output: Audio Control: A control that plays an audio file. Description: An Audio control plays a sound clip from a file, a recording from a Microphone control, or the audio track from a video file. Steps: 1. Add Audio control. 2. On the Content tab, click or tap Media, and then click or tap Browse And select the audio from local device. 3. Set Media property of audio to the name of audio file. Output: Video Control: A control that plays a video file, or a video on YouTube. Description: A Video control plays a video clip from a file or from YouTube if you specify a URL. Example: For adding a YouTube video Steps: Add video controller and set its Media property to the URL link of that YouTube video. (add URL in quotes) Output:

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.