I have a solution that is nearly 32 MB in size. I want to divide the solution into segments because the solution contains various kinds of components, such as tables (and their metadata), choices, connection references, custom controls, dashboards, pages, plugin assemblies, plugin steps, processes, reports, security roles, sitemaps, apps, and web resources. I am searching for the best practice to split the solution in order to reduce its size for the import/export process. Is there any advice that could help in this process or any best practices that someone could offer to assist, please?
Hi, Our team analyzed your requirements because you only describe what your solution contains, but not the connections between the contents, such as whether there is a relationship between Entity A and Entity B, whether the Plugin references other resources, and so on. So our team can only give a generalized solution. Solutions are divided by component type without risk of cross-dependency. For example, one solution contains all Forms, another contains all Plugins, and a third contains all Processes. There is no risk of cross dependency of these different components. Here is the official documentation on using segmented solutions https://learn.microsoft.com/en-us/power-platform/alm/segmented-solutions-alm https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-solution#create-a-segmented-solution I hope my answer is helpful to you! If you have any other questions, please feel free to contact me. Best Regards, Rudy Zhang
Was this reply helpful?YesNo
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.
92
Share
Report
All responses (
Answers (
