DynamicsMinds – ALM for Dataverse using Azure DevOps Pipelines
I will have a session called “ALM for Dataverse using Azure DevOps Pipelines”
2 Comments
Cookies & Privacy
This site uses cookies. By continuing to use this website, you agree to their use.To find out more, including how to control cookies, see here: Privacy Policy
ACCEPT
Privacy & Cookies Policy
Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Hi Benedikt, I’m a bit late to the Power Platform ALM conference, but have found your blogs to be very insightful. I was wondering whether you would be able to share your approach to rollbacks. For example, let’s say there are three environments (DEV/TEST/PROD). A solution is deployed to PROD that needs to be reverted due to some issues. However, you have already commenced development on the next feature within the development environment and can’t go through the DEV->TEST-> PROD deployment process due to unfinished changes. How could one go about implementing a rollback strategy via the use of YAML pipelines?
Hej Ty,
in general rollbacks in the Power Platform are rather complex or even not possible.
If you (as one should) store your solution unpacked in your repository you could pack an older version and deploy that to Production.