cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
steve-platz
Frequent Visitor

Incrementally moving to a single managed solution

My company has been using unmanaged solutions for many years to deploy changes between our dev, test, and production environments. A new unmanaged solution is created for each sprint, changes are added to it, and it is deployed across each environment. Now, I'd like to move to a more controlled ALM solution using managed solutions and automated deployments with Azure DevOps.

 

To help reduce risk, I'd like to incrementally deploy a managed base solution, but I'm unsure if this is a good idea. To do this, I would like to add the custom entities we've created to the solution, one at a time, and push them up through production, then repeat with the next entity. So, if there were three custom, unmanaged tables (Table 1, Table 2, and Table 3), the first deployment would convert Table 1 to managed, adding in any required components, the second would convert Table 2 to managed, and so on.

 

Are there any pitfalls to this approach that I need to be aware of? The Microsoft documentation mentions adding all unmanaged customizations and deploying with a single solution, so I want to be sure I'm not backing myself into a corner in some way by slowly building up over time.

1 ACCEPTED SOLUTION

Accepted Solutions

Yeah, you're on the right track here for sure.

 

What I'd add is that when dealing with managed solutions it is the "stacking" where you run into complications, as opposed to the initial push; your second managed solution install has far more ways to go wrong than the first.

 

So instead of copying Prod before every release, copy it just once and branch into a Prod and a "Shadow Prod" where you continue to push to Prod for a little while unmanaged because that is safe and comfortable and you know what you're in for, but at the same time you push out a couple releases in a row managed to 'shadow prod'. With a bit of luck, you'll hit conflicts like mismatched publisher prefixes or dependency blocks or other failed imports that will let you get a sense for the quirks without ever putting prod at risk. Or, maybe your solution is just so well-managed and straightforward that you hit no issues at all, in that case you can switch to managed without any hesitation knowing you've really tested it out.

 

Beyond that, your headaches in the future will all be about cross-solution layering. So, unmanaged customizations on top of your managed ones; multiple managed solutions that have conflicts or overlap; things like that. For as long as you are monolithic, as you say, these issues will be rare. Just know the community is always here to help if you run across a nasty issue and need some advice!

View solution in original post

6 REPLIES 6
cchannon
Multi Super User
Multi Super User

You're not backing yourself into a corner, but it does seem like you're creating a lot more work for yourself than is necessary.

 

When you import a managed solution with a given component (a table, for instance) and that component already exists in the target environment as unmanaged, Dataverse will automatically convert the component to managed (i.e. the managed solution always wins). This is true whether you are importing one, three, or twenty components at a time.

What benefit are you looking for by converting them to managed one at a time?

steve-platz
Frequent Visitor

@cchannon That was my understanding, what I saw from testing, and why I came ultimately went down this path. The benefits I'm looking for are risk mitigation (smaller, incremental changes to managed) and the ability to not have to switch over all unmanaged components to managed in a big bang. I'm a single developer on a medium-sized deployment and need to balance changing to managed with ongoing customizations + other commitments.

Ok, then before you start down this path, a bit of advice: be sure you are ready. Doing these entities one at a time isn't going to mitigate much risk for you because once you go managed on anything it is quite hard to go back.

 

I am strongly in favor of using managed solutions, but I have been doing it for years and I know the pitfalls. If you want to dip a toe in the water, I think that's a good idea but don't do it by going partially managed. Instead, make a copy of your target environment and go all in as managed in the copy, while changing nothing about your process in the real thing (unmanaged). Then go for one or two more releases like that and see how the two environments differ: managed to managed and unmanaged to unmanaged.

 

This will let you get a feel for it and mitigate risk by not actually touching production until you are totally ready.

@cchannon That's a great idea. I think pushing managed/unmanaged to dual environments would be a great way to build up the managed solution while feeling more comfortable about the eventual switch. It seems best to make a copy of production before every managed deployment, to ensure there will be no issues when the actual switch occurs.

 

Deployment PipelineDeployment Pipeline

 

Outside of needing to maintain a copy of the unmanaged solution so you can make changes in the future, and the potential issues that can come with layering and dependencies, what other pitfalls should I watch out for? I plan to start with a single, monolithic solution.

Yeah, you're on the right track here for sure.

 

What I'd add is that when dealing with managed solutions it is the "stacking" where you run into complications, as opposed to the initial push; your second managed solution install has far more ways to go wrong than the first.

 

So instead of copying Prod before every release, copy it just once and branch into a Prod and a "Shadow Prod" where you continue to push to Prod for a little while unmanaged because that is safe and comfortable and you know what you're in for, but at the same time you push out a couple releases in a row managed to 'shadow prod'. With a bit of luck, you'll hit conflicts like mismatched publisher prefixes or dependency blocks or other failed imports that will let you get a sense for the quirks without ever putting prod at risk. Or, maybe your solution is just so well-managed and straightforward that you hit no issues at all, in that case you can switch to managed without any hesitation knowing you've really tested it out.

 

Beyond that, your headaches in the future will all be about cross-solution layering. So, unmanaged customizations on top of your managed ones; multiple managed solutions that have conflicts or overlap; things like that. For as long as you are monolithic, as you say, these issues will be rare. Just know the community is always here to help if you run across a nasty issue and need some advice!

Thanks! I appreciate you taking the time with me on this. 

Helpful resources

Announcements

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!      

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Community Roundup: A Look Back at Our Last 10 Tuesday Tips

As we continue to grow and learn together, it's important to reflect on the valuable insights we've shared. For today's #TuesdayTip, we're excited to take a moment to look back at the last 10 tips we've shared in case you missed any or want to revisit them. Thanks for your incredible support for this series--we're so glad it was able to help so many of you navigate your community experience!   Getting Started in the Community An overview of everything you need to know about navigating the community on one page!  Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Community Ranks and YOU Have you ever wondered how your fellow community members ascend the ranks within our community? We explain everything about ranks and how to achieve points so you can climb up in the rankings! Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Powering Up Your Community Profile Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile. Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Community Blogs--A Great Place to Start There's so much you'll discover in the Community Blogs, and we hope you'll check them out today!  Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Unlocking Community Achievements and Earning Badges Across the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. Check out some details on Community badges--and find out more in the detailed link at the end of the article! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Blogging in the Community Interested in blogging? Everything you need to know on writing blogs in our four communities! Get started blogging across the Power Platform communities today! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Subscriptions & Notifications We don't want you to miss a thing in the community! Read all about how to subscribe to sections of our forums and how to setup your notifications! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Getting Started with Private Messages & Macros Do you want to enhance your communication in the Community and streamline your interactions? One of the best ways to do this is to ensure you are using Private Messaging--and the ever-handy macros that are available to you as a Community member! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Community User Groups Learn everything about being part of, starting, or leading a User Group in the Power Platform Community. Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Update Your Community Profile Today! Keep your community profile up to date which is essential for staying connected and engaged with the community. Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Thank you for being an integral part of our journey.   Here's to many more Tuesday Tips as we pave the way for a brighter, more connected future! As always, watch the News & Announcements for the next set of tips, coming soon!

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Users online (3,288)