Answered

Using SharePoint Lists as Backend

(0) Share

Report

Posted on by kilaj1

257

I have a App I'm creating that has 10 pages, 9 repeating tables and about 90 additional fields. I was initially creating this with the input fields directly in the PowerApp, but then I realized, what's the point when I need it in a SharePoint list anyway to store the data for other activities (flows and reports).

From what I can gather every Repeating Table would need its own list and would have a field with an ID that would correspond to a ID in a Master List.

My question is, would it make sense to make the Master List contain all the other fields, which are spread across multiple pages. or create a list for each page (minus the repeating table on it)?

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

joeinmay 205 on at

Like (0)

Report
Copy link

Link copied!

You can still try one single list with all the columns.
Create a screen with a gallery.and adjust fields as needed to fit horizontally. Tidy it up as needed.
Duplicate the same screen 9 times as in your case.
Each screen gallery can use a common variable for filter, lookup, sort....etc
Goto each screen and change the values for label or text.
You can include the Next and Back icons to navigate.
Rest you can imagine what to do. This is a workaround

Something like this;

Was this reply helpful? Yes No
JR-BejeweledOne 5,836 Moderator on at

Like (0)

Report
Copy link

Link copied!

Don't forget about delegation. If you anticipate that your list will grow beyond 2000 entries, then you don't want to use SharePoint unless you can start with a delegable query that brings in less than 2000 rows. It causes all sorts of problems.

Was this reply helpful? Yes No
kilaj1 257 on at

Like (0)

Report
Copy link

Link copied!

Thanks, Im going to try the one master list but still separate the repeating tables. It will defiantly not pass the 2000 limit.

Was this reply helpful? Yes No