Skip to main content

#msdyn365bc - Delete extension data.

Hi Readers,

In this article we will test out a new feature released with 2020 Release Wave 2.

With this feature, administrators can delete extension data in production or sandboxes, either because an application is not in use or, more commonly, because there is a desire to reinstall it from scratch without data—for example, after testing or trial.


This is important feature for SaaS customers as size of database is important and removing data which is not required is important to keep tenant clean and also keep database size reduced.

  • On the Extension Management page, when you select an extension and choose to uninstall it, Microsoft have added a new Delete Extension Data option in the uninstall dialog box.
  • If you select this option, and confirm both at selection and subsequently on selecting Uninstall that you understand that data will be deleted, the service will delete all data owned by the extension. 
  • This is equivalent to invoking Sync-NavApp with the "clean" mode (on-Prem).

1. Open Extension Management Page and Select Uninstall for the Extension that you want to remove.

2. A New option is now available for Deleting Extension Data. (it will be disabled by default)

3. Choose Enable Deleting Extension Data, if you would like to delete data associated with that extension.

4. System will prompt you for first confirmation about Enabling Deleting Data with extension.


5. If you choose yes a Next confirmation will be asked to continue the Remove the data. Action is irreversible.

6. If you choose yes Extension will be uninstalled.

7. Last step is to Unpublish Extension.


If you don't choose Deleting Extension Data, the Uninstall Extension will preserve data and schema.

Let me know how you feel about this feature.

Stay Connected.

Regards,
Saurav Dhyani

www.sauravdhyani.com

Comments

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

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.