***The product & category selected was wrong, it should be LCS function for D365 Finance & Operation***

Since using D365, deploy the production environment has become a headache, especially recently, it seems your team have made changes to the deployment of the UAT(sandbox) environment. The deployment time is longer than before, and each deployment package must to do ’Mark as release candidate’ which will deploy to production environment, after a long wait for the UAT deployment complete, it also takes a very long time to load the packages list when manual deploy the production environment. In short, everything is very inconvenient...

Can your team make some automation changes to the schedule tasks for the production deployment?

For example, a package we deploy to UAT knows that it will be used to deploy to the production environment, the name of this package is called [PROD]20220324, when the UAT was started to deploy, the name has been fixed and there will be no change, so when we open the production environment deployment scheduler dialog, just three parameters need us to input,

1) the sandbox environment (just no change as right now)

2) the package name which is deploying(new request) in UAT or deployed in UAT, no need to lookup or list out the packages to the grid, just manual input. Of course, it would be better if you could simply check if the package we filled in exists in the UAT.

3) Downtime start (just no change as right now)

Of course, we will estimate the approximate completion time of UAT deployment by ourselves. The downtime start mentioned above will definitely be after the UAT deployment was completed. When the downtime start is up, if the system detects that the package has not done ' Mark as release candidate ', it will automatically complete the process for the package. In addition, the deployment of UAT may fail. When the scheduled deployment for the production environment detected the package has not been successfully deploy, the deployment task of the production environment is automatically cancelled.

The above is our strong suggestion, the automation is logical and no risk for the production deployment, and the changes should be not very complicated, I hope your team can make such a convenient function, thank you.