Inspection App with many inspection types

[ClayCollins]

I posted here initially, but realized that thread was marked as resolved, so it may not have been the best place to post my question. But here's the original: https://powerusers.microsoft.com/t5/Building-Power-Apps/Add-a-new-column-to-the-sharepoint-list-from... 

I'm trying to create an app with many inspection types (30 different inspection types), and quite a few have many data points (over 200 different questions). In building just one of these inspections has been a lot of work, and I'm about halfway through the 3rd of 30. But now I've started to wonder if I'm going about it the best way. 

My basic approach thus far:

I've created a SharePoint List for each inspection, with each column being one of the data points to track (with abbreviated names). Obviously this is quite tedious to create 200+ columns. Then, in the Edit Form side, I'm using DataCards and customizing the names to be more clear as to the question. 

And I'm creating a different Form, depending on which Inspection type was selected from the drop-down. 

With Delegation concerns in mind I'm also following this approach when answering the questions.  ( https://www.practicalpowerapps.com/delegation/power-apps-delegation-sharepoint/ ) 

Since Building a SharePoint List from importing an Excel table makes for further PowerApps building a nightmare (it doesn't call the columns what you named them in Excel, but rather they're referenced as "field_01", "field_02", etc) I thought maybe some approach wherein the questions are based off a SharePoint List would be time efficient (since you can be copy and paste from Excel to SP List, when in Edit Grid View, without issues like above). 

I went through the tutorial today to learn about making a dynamic form as described here: https://www.matthewdevaney.com/power-apps-dynamic-forms-generate-forms-from-a-questions-list/ 

But I'm wondering if this is going to be effective for recording an inspection, since it looks like each answer gets placed on a separate line of the SP List. So would that mean that each inspection performed would need its own SP List??

Please any input on this would be appreciated, and a little more direction about whether Parent -> Child setup is best practice here. And if so, what resources you'd recommend to help me comprehend and implement. 

[EddieE]

@ClayCollins 

Maybe have a think about the data you need to collect for each form. Do yo7 need to collect every question as data or could you collect, say 10 data fields like 

FormName | Inspector | InspectionDate | … ( up to maybe 10 fields)

then just store this in a SharePoint Document Library with a PDF of the form and all the other questions answered?

If you had commonality across the various forms for these 10 fields then you could just use 1 library. You could then use a form platform like Cognito Forms to build out your forms and use it with Power Automate to collect the data. Cognito has a Standard Power Automate connector which doesn’t require a premium licence.

Another issue you may run into is the column limit in SharePoint. It’s based on the column types used but you can check it out here

https://learn.microsoft.com/en-us/sharepoint/install/software-boundaries-limits-2019#column-limits

These are just a few tips but I could give you a few more if these are what you are looking for?

[ClayCollins]

@EddieE  

I would need to access the data again, since I use it later to create a QR Code, as described here 

So I don't think putting the data into a static form/document would suffice. Although, getting it into a document is also a goal, the data would need to remain dynamic. I appreciate the link to the column limitations, as that was insightful. 

Any other thoughts on how this could be built?

 @mdevaney