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.

Regards,
Saurav Dhyani

www.sauravdhyani.com

Comments

Popular posts from this blog

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.

🚀 Exploring Vibe Coding with GitHub Copilot for Business Central.

Hi All, In a recent #BCOpenDiscussion session, we delved into the fascinating concept of Vibe Coding —a new way of building software where developers collaborate with AI (like GitHub Copilot) to co-create solutions.  The session covered practical setup, how AI understands context, and even touched on Microsoft's new Model Context Protocol (MCP) integration for enhanced learning. Let’s break down the journey, step by step.