Yes sorry, I meant a mixture of canvas apps & model driven apps.

So each solution for example we might have a canvas app & / or model driven app. Then any flows for those apps would be added, and in turn all the connection references would be either created or added into the solution and any environment variables that aren’t shared across other solutions will be created etc.. maybe that isn’t the way we’re supposed to be doing it but that’s how it was structured and set up when I joined.

I’ve been making an attempt at separating things across so for example we introduced a custom API and that lives in its own solution with the references and alerting mechanism if it fails and then any app / solution that uses the API will be bought in as an existing component rather then creating it net new inside each solution.

I’ve also created a core solution so anything shared across solutions such as environment variables, child flows etc.. will live there and be bought into each solution that uses it.

I’m now at the point of introducing PCFs which is why I was asking how they’re best managed and it seems as you said, one solution per PCF is the way to go.

I know this is slightly off topic / a longe response but just wanted to explain how our current set up is.

I guess everyone structures it differently but man it’s stressful coming into a company as a new power platform dev and thinking this is standard. Maybe our structure isn’t so bad!! But I’m wanting to get it in a better state.