You’re offline. This is a read only version of the page.
Announcements
225
I have components in an unmanaged solution that I was using to do a proof of concept. They are now ready to be implemented as part of an existing unmanaged solution. I've read some posts that say I have to recreate them in the target solution to ensure publishing/dependencies are correct. I read in this post Solved: Solution Components Creation Guidance Needed - Power Platform
Community (microsoft.com) that I can use the Save as to bring them into the target solution and it will eliminate dependencies.
Would some please confirm the best practice? Is it to recreate or use Save as.
The components are - Business Process Flow, Cloud flows, forms, a new table and new views as part of a Model Driven App (Customer Service).
Hi @rg0173
Both options work in different situations.
Recreating components ensures clean dependency management and avoids potential issues that might arise from carrying over unwanted dependencies.
On the other hand, using the "Save As" method is significantly faster.
If the publisher of both solutions is the same, you can directly add the components using the "add existing" component option. Just be careful to check if they have any additional dependencies, for example by clicking on "add required objects."
Also, once all the components are in the solution, remember to run the solution checker to double-check for any additional dependencies.
So it’s really up to you. If you know the source of the components and have dependencies under control, go ahead with "add existing." I usually use that approach to have different unmanaged solutions for development, and once the development is complete, I add the components to the main solution.
If my response resolved your issue, please feel free to mark it as the solution by clicking accept it as a solution.
If you liked my solution, please give it a thumbs up.
This helps others find the answer more easily.
Connect with me: LinkedIn
Share
Report
All responses (
Answers (
