Finance | Project Operations, Human Resources, ...

Update Prod environment

(0) Share

Report

Posted on by tdgscorpion

107

Hello when I try to update Prod environment with deployable package already updated to UAT. I receive this message.

When deployed the package was and UAT was on 10.0.25 but later UAT was updated to 10.0.27. Prod is also 10.0.27.

But is this message means that Prod will be downgrade to 10.0.25

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Komi Siabi 13,093 Most Valuable Professional on at

Like (0)

Report

Hi ,

It is obvious that the package you are picking is 10.0.25 even though your UAT in currently on 10.0.27

Confirm this and revert.

Was this reply helpful? Yes No
YY Lim 960 on at

Like (1)

Report

Hi, this is because self service deployment is not only deploy the package. but it is snapshot deployment , what it means, it will be exactly the same with your sign off environment, this is the reason you not mark release candidate at the asset library package anymore, but on the environment itself, means you are deploying what you sign off on that environment.

I don't think if you click confirm, it will able to deploy because downgrade is not allowed if not mistaken or it will have error when it is trying to deploy. Another option you can do is sign off again from the UAT that you updated to 10.0.27. then it will have both package the the update version (assume is the same with your production) but I would suggest the regression testing because your testing is carry out on 10.0.25 version when you sign off, the 10.0.27 version might impact the solution.

Was this reply helpful? Yes No
id365font 398 on at

Like (0)

Report

Nowadays when you update Production environment you are applying an "image" from UAT environment in terms of code. You are applying the whole code, either standard and customized code. So what you have to do is to mark as released candidate the last applied package (in your case, the service update package to 10.0.27). This "image" will include customization and standard code so you production environment will upgrade to 10.0.27.

Was this reply helpful? Yes No
Suggested answer

Alireza Eshaghzadeh 14,679 Super User 2025 Season 2 on at

Like (0)

Report

Hi tdgscorpion,

Ref to the screenshot, deployable package (e.g. merged code package) is created on 10.0.25 version (10.0..49.40). Ideally you need to use same version on DEV, UAT and Pord when you create a deployable package.

I dont think that it will downgrade the product version while it can change/remove customizations or ISV since target version has lower version than current version. You can evaluate to create a new deploayble package on current version in UAT with changes that you want and then perform a thorough test, once the test is approved, you can deploy it in production.

More information about applying update to a Prod environment:

docs.microsoft.com/.../apply-deployable-package-system

Was this reply helpful? Yes No