Skip to main content

What's New in Update 17.3 for Business Central Online?

Hi Readers,

Microsoft have released 17.3 for Business Central SaaS customers. 

The Update will be applied on all SaaS Tenant in coming weeks. Update is already started rolling out on SaaS Customers.

With this cumulative update Microsoft have added some features which were requested by community on Ideas website.

Other MVP's & Bloggers have written detailed article about these Feature changes.

Feature changes

1. Restoring environments in Business Central admin center.

  • All databases are protected by automated backups that are continuously created and maintained by the Azure SQL service. 
  • The backup retention period for Business Central databases is set to 30 days for both production and sandbox environments.
  • Environments can only be restored if the customer has a paid Business Central subscription.
  • Each environment can be restored up to 10 times in a calendar month.
  • It's not possible to use the Business Central administration center to restore an environment that was previously deleted.
  • An environment can only be restored within the same Azure region and country (Business Central localization) as the original environment.
  • A production environment can be restored to either a Production or Sandbox type environment. A sandbox environment can only be restored a Sandbox type environment.

When restoring an environment, you'll create a new environment that the database backup will be restored to. You can't use the same name for two environments of the same customer. So if you want the restored environment to have the same name as the original environment, rename the original environment before you run the restore operation. For example, you could change the name to include DONOTUSE.

How To Restore an Environment - 

  1. Open Admin center.
  2. Select Environments and then open the environment you want to restore.
  3. Select Restore.
  4. In the Restore Environment pane, specify the date and time in the past to which you want to restore the environment.
  5. Select the type to be used for the restored environment.
  6. Specify a name for the restored environment.
  7. Select Restore.

Read More in MSDN

2. Use Shortcut dimensions in G/L Entries for Financial reporting.

As Microsoft have Shortcut dimensions are available in Journals pages, Microsoft have also added all shortcut dimensions in G/L Entries page (as variables).

If you have a custom where you added this field, then its time to remove from P.T.E.

You can read detailed blog about this change in Yun Zhu blog.

3. Signal from web service key authentication added to Application Insights telemetry for partners

Read in MSDN

4. Handle Price List Exceptions with Allow Updating Defaults.

Read in MSDN

Other Good News in 17.3 - 

  • Basic Authentication - (Web Service Access Key) removal for Business Central online has been postponed until April 2022. 
  • Snapshot debugging is now enabled in production environments.
  • Switch Browser to Microsoft Edge

    • It’s time to switch your Dynamics 365 Business Central browser to Microsoft Edge.
    • On April 2, 2021, Microsoft will remove Internet Explorer 11 and Microsoft Edge Legacy browsers from the list of supported browsers for the Business Central modern clients. 

Hope you find information useful. Let me know your views as comment to this article.

Saurav Dhyani


Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.

NAV 2013 Upgrade Part III - Data Upgrading.

Hi all, As per agenda we need to discuss the data upgrade in NAV 2013. The process is similar to what used to be till NAV 2009 R2 but with some changes. Let's start the process. Remember -  1) You can only upgrade a database to NAV 2013 from NAV 2009 SP1 / R2 SQL Only. 2) The Synchronization of users with SQL Server is no more required.