web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Power Pages - General Discussions
Answered

One solution OR multiple solutions for Pages/Flows/Apps/Dataverse

(0) ShareShare
ReportReport
Posted on by 58
I need advice on how everyone is using Solutions and solution export/import with the power platform. My main deliverable is a Power Pages site, however to support this I have a number of Power Automate flows and a Power Apps Model app to administer the ‘back end’. Everything is in Dataverse.

Microsoft Support gave me advice that I should have everything in one solution. However, this doesn’t fit with the lifecycle; the model app and flow change far more often than the pages site.
Do you have one solution or many?

What would seem to work for me are two solutions
  1. Dataverse / Flows / Model app. Usually, the database, flow and management are created first.
  2. Power Pages: usually, the front end is built last, once the flow, database and admin can support it.
So, two solutions seems to make sense to me, but this is against the advice from MS Support who told me to use just one.
Categories:
I have the same question (0)
  • Verified answer
    Michael E. Gernaey Profile Picture
    51,550 Super User 2025 Season 2 on at
    One solution OR multiple solutions for Pages/Flows/Apps/Dataverse
     
    They would not know whether you should or should not, they are not experts in using the platform itself.
     
    Its up to you. Having them all in one solution is fine, no matter how often you update the flow etc as it has no impact on the site what so over as it will only update the stuff that has changed.
     
    If its re-usable across multiple other projects, then it should be in a base solution to be shared, otherwise together is fine, but not because of any other reason than, I have no idea if its shared anywhere else.
     
    Another thing to take into account, is not so much how often things change, but how many different people you have working on it. Everyone can create patches and work on the exact same solution at the same time, so its not a big deal to have all 3 of these together. separating them does not make sense to me and it doesn't matter how often those 2 things change and that the Site does not.
     
    But these are limited click down details, but rate of change is not something I use 999.9999999% of the time. Sharability and re-use is.
     
    If these are all dedicated to exactly the same thing.. then yeah I would put them together.

    If these suggestions help resolve your issue, Please consider Marking the answer as such and also maybe a like.

    Thank you!
    Sincerely, Michael Gernaey

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.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Chiara Carbone – Community Spotlight

We are honored to recognize Chiara Carbone as our Community Spotlight for November…

Leaderboard > Power Pages

#1
Fubar Profile Picture

Fubar 50 Super User 2025 Season 2

#2
Michael E. Gernaey Profile Picture

Michael E. Gernaey 38 Super User 2025 Season 2

#3
Jerry-IN Profile Picture

Jerry-IN 30

Last 30 days Overall leaderboard