This video will demonstrate how to delete package from UAT/Prod environment in D365fo incase you don't want any particular package over there
Steps as per Microsoft Documents:- 1.Create a file that is named ModuleToRemove.txt. 2.In the file, put the name of each module that you want to remove on a separate line. Make sure that you've completed the prerequisites for each module that you're removing. 3.Create a valid deployable package, and put the ModuleToRemove.txt file in the package\AOSService\Scripts folder. 4.Upload the package to the Lifecycle Services asset library. Wait for the asset to finish validation, and review any warnings that are shown on the Asset Details panel on the right side of the page. 5.Install the deployable package. For more information about how to install deployable packages, see Apply updates to cloud environments. 6.Verify that the package was uninstalled before you complete this procedure in a production environment. You can also find out detailed steps over Microsoft document on following link:- https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/deployment/uninstall-deployable-package#uninstall-a-package-1 Note: Don't unzip the file while putting txt file over thereImport Database from UAT/Production to cloud-hosted or dev environment | D365 Finance and operations
Update: If following method is not working have a look at this Changes in SQL Script to restore bacpac file for D365FO Many times to debug the Production environment issues we might need live data to address that issue in such case first of all we need to refresh the UAT/Sandbox database with the Production environments database and then afterward we need to export the UAT database to the Asset library from where we can get bacpac file for that UAT database which is then to be imported in your cloud-hosted or one-box environment. This blog and video demonstration will help you to restore your production or UAT database to a cloud-hosted environment. Step 1: Rename existing db In this step, we need to rename the existing AxDB for safety purposes. Just go to the SSMS application and execute the following command:- ALTER DATABASE [ip_ent_site] SET SINGLE_USER WITH ROLLBACK IMMEDIATE GO ALTER DATABASE [ip_ent_site] MODIFY NAME = [ip_ent_site_new] GO ALTER DATABASE [ip_ent...
Comments
Post a Comment