Environment Cleanup

[waldo1001]

A guideline to implement "Environment Cleanup" of your module. There is little to no documentation about it on Docs, but needs proper attention

[curateideas]

What do you have in mind when the "cleanup" should happen?

[waldo1001]

When an environment is copied to a new one

[curateideas]

@waldo1001 : While reading you blog post, I had a small deja vu. I stumbled upon the cleanup of settings in the Microsoft Docs a few weeks ago when preparing a presentation about the restore-function in BC Admin Center. And there they mentioned the exact same setups:

https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/tenant-admin-center-backup-restore#considerations-and-limitations

So it seems Microsoft uses them in case of restoring an environment (which seems to be a sort of 'copy' of an environment, too).

[PeterConijn]

I think this is an important, yet often overlooked, process in these copy procedures. I am linking your (@waldo1001) post about this on Dynamics Community, since it has important information: link

Like Waldo said in that post, the environment triggers (most likely) only work in SaaS. For OnPrem, we intend to integrate this in the SQL Copy script we use for copying, but since we live in a multi-app world, this will need some checks on whether an app is installed.

Either method will also need maintenance if new tables (that fall under the "must clean/disarm" scenario) are added. This means that we will need to raise awareness in our feature write-ups (like we have for "does this need install/upgrade code"?) and development teams too.