Answered

Multiple, independent data sets in one UX; best practices

(1) Share

Report

Posted on by HorejsiPower

I am looking to incorporate 4 separately managed datasets into one UX. I currently have a full solution (multi-screen app with automations) for one of the datasets and am trying to understand best practices for incorporating the other 3. I would like to have a centralized search screen and then custom interaction screens based on each lists' needs.

Is it best to include everything in one app and one solution? Should I separate out the datasets into their own apps and create a 1-screen search app that connects out to the others (but still roll up in one solution)? Just trying to understand best practice concepts before I dive in and have to rebuild because I picked the wrong way.

Details about my existing setup:
4 editable SharePoint lists - all have unique edit permissions, all have read permissions.

4 accumulating SharePoint lists - data is accumulated and tracked here for capacity.

17 automations based on status changes in the existing solution workflow.

10 environment variables point to my SP site, existing lists, deeplink pieces, etc.

Thanks!

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Scott_Parker 1,090 on at

Like (0)

Report
Copy link

Link copied!

It sounds like the applications each go with a different process. If so, I would separate them into different apps. If they aren't separate processes, then I would build them together in the same app. Having them in separate apps will make your solution much more modular, make development easier, reduce load times for your users, etc.

Was this reply helpful? Yes No
HorejsiPower 13 on at

Like (0)

Report
Copy link

Link copied!

Thanks @Scott_Parker! That makes sense. If I want a centralized search page, would you recommend I build that as a standalone, and then connect out to the individual apps from that central one?

I'm assuming you're implying that this would all live in the same solution as well?

Was this reply helpful? Yes No
Verified answer

Scott_Parker 1,090 on at

Like (0)

Report
Copy link

Link copied!

Yes, I would recommend building that as a standalone app, as well.

I'm afraid I can't give you a good answer about splitting them into solutions because I haven't made use of the ALM functionality of Power Platform where you create "managed solutions" to load into the production environment. The good thing is that since solutions aren't "folders" where you store something but are instead groupings of apps, flows, etc. that are distributed together, it won't be too hard to split or recombine them into one or many solutions, as needed. You can add the same flow or app to many different solutions.

With that in mind, I would say keep them together in one solution and make adjustments in the future as necessary.

Was this reply helpful? Yes No
HorejsiPower 13 on at

Like (1)

Report
Copy link

Link copied!

Thanks for the follow up and your thoughts @Scott_Parker. I really appreciate it!

Was this reply helpful? Yes No