All you need to know about Deployment in Production environment in D365FO
Hey folks,
Previously I wrote an article which explained how to Create and Deploy a package in D365 in Test Environment. Link to that article is here.
Today's article is mostly related about the deployment in Production environment as the process is slightly different and a little bit confusing too.
This article will answer following questions.
Apart from that, I will also mention some important key points for a smooth deployment.
So, Let's get started with the deployment process first.
2. Click on Full details button of the Test instance.
3. Click on History>Environment changes
4. There you will find the status of every package which was deployed on your Test instance. From this list you have to select a package which want to move forward into Production environment.
5. You can only move such a package to Prod whose status is completed in this history log. To move a package to Prod instance, you need to select that package here and mark it as release candidate.
6. It will ask you for confirmation, so click on Yes button.
After you will mark it as release candidate, Is Release Candidate value will be changed to Yes.?The whole page will be refreshed once and you will be able to see the change.
Now, it's time to apply that update to Prod instance.
7. For that open up Prod instance.
8. Click on Maintain > Update Environment
9. In the pop-up window shown, select the Test environment, select the package you want to move to production, select the down-time start and click on Schedule button.
10. Click on the confirm button.
It will show the following screen afterwards
The Pre servicing will automatically start the scheduled time which will be followed by Completion and Post servicing steps.
Now, to answer the 2nd question of checking the Platform and Product version of your instance, Just open the instance in the browser and Click on ? button on the top right hand corner and then click on About.
You can apply Application deployable package and Platform and application binary package update both into Test and Prod instances. The difference between the two is that you create a package from your dev instance which is called Application deployable package and all the updates from Microsoft itself are of the type Platform and application binary package.
?
You can deploy a package created from Dev instance with Product and Platform version to a Test instance with higher Product and Platform number but you cannot move such package to Prod instance. This is a kind of bug, I believe as per today when I am writing this article and may be resolved by Microsoft in future. I will write a seperate article explaining how to increase the Product and Platform number of your instance.
?I hope this article will help newbies to learn something and deploy their packages into D365 flawlessly.
Disclaimer: Above mentioned all information and analysis is based on my own experience and observation, so someone may find something different based on their own experiences.