Notifications
Announcements
No record found.
I have a production environment on version 10.0.19. I have a package built for version 10.0.19. I have scheduled the package to be deployed to production. In the small box in LCS that has information about the upcoming update it says:
Hi nmkloster,
could you share a screenshot?
If you have a "self service" environment (like most systems are today), your whole UAT version will be deployed to production. This includes the MS application and your customizations from the UAT system.
So if this is the case, the 10.0.22 comes from your UAT system.
If you need any more inputs, let's start with a screenshot so that we can see what you're seeing. Thanks!
Yes, the UAT is version 10.0.22. I kept this information back intentionally. Am I understanding you correctly, that the version 10.0.22 (and 10.0.995.69) is just information about the AUT environment that was used to mark it as Release Candidate? It is still just the package that was deployed to UAT that will now be deployed to production?
The reason is that an error was discovered while we are getting ready to upgrade and so development and UAT is already on version 10.0.22. I guess in thery I could have managed to code something that compiled without errors in the pipeline targeted at versions 10.0.19 while still containing errors that we now might not catch in UAT on version 10.0.22?
Hi,
I don't think that your screenshot is from the screen that you mention in your question. Could you please the correct screenshot? Thanks!
As I wrote, it's likely that your whole UAT will be promoted to Prod, including Microsoft update and your code.
Also, if there's any other information that you're holding back intentionally, could you please share it? Otherwise it's not so easy to try to help, and we might not be able to answer your question.
It is the screen I'm looking at. It is the full details page in LCS of the production environment.
Ah, you're right. I was somehow expecting to see more information about the update.
Anyway we can see that it's a Self-service environment. And this means that UAT-Prod deployment always releases the whole UAT application to Prod. So it's not just your latest deployable package that will be applied, it's a snapshot that contains the entire application.
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/deployment/updateenvironment-newinfrastructure#promote-an-update-to-production-environments
Microsoft has introduced the image-based, update process. As was discussed earlier in this topic, as packages are applied to sandbox environments, Microsoft creates images that are given an Update name value. This value represents the whole runtime, including Microsoft code and all custom code as a single unit. When customers want to promote a change to a production environment, they select an update from a sandbox environment's history. The whole runtime is then moved to the production infrastructure as is and should better safeguard against regressions.
Thank you. I'd better stop the update until we have tested update 10.0.22 in UAT fully then.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
André Arnaud de Cal... 490 Super User 2025 Season 2
Martin Dráb 429 Most Valuable Professional
BillurSamdancioglu 241 Most Valuable Professional
