The last solution architecture we are going to look at is very similar to the Feature Solution Architecture but instead puts a twist on it – the Team Solution Architecture. In the Team Solution model, solutions are deployed by the teams that create them. The teams can be of any size, but generally, their deliveries … Read More
Category: Architecture
PowerApps Solution Architecture: The Feature Solution
We’ve looked at the All-In-One and Component Solution Architectures and now we’re going to talk about the Feature Solution model. As shown below, the feature solution model is based upon areas (features) that you deem to make sense to your organization. Although Marketing and Service are highlighted below as PowerApps terms, these features could include … Read More
PowerApps Solution Architecture: The Component Solution
Continuing from our previous post on Solution Architecture in PowerApps, we’re going to move forward into the Component Solution model. It should be noted that these names are not written down anywhere and are merely created by me. I’ve used the Component Solution model many times over with great success as it works with small … Read More
Managing Distributed PowerApps Development Teams
That title is quite a mouthful, and I did try to collapse it into a few succinct statements but couldn’t make it work. But this is a question I see all the time and like anything, there are a few ways to handle it. The Problem You have a number of developers working on multiple … Read More
PowerApps Solution Architecture: The All-In-One Solution
After many years of building apps on the Dynamics/PowerApps platform, I still get asked about how to architect PowerApps solutions. How do I group components? What’s the best solution for pipelines? What solution model works best for big or small teams? How do we future-proof ourselves so we never have to change our solution ever … Read More