I’m doing rental for machine. Before we deliver to our client, we have to do some pre-delivery inspection to make sure the machine is in good condition and as a proof that we check it.
But there’s 76 questions in total for four groups of inspection.
Every question can be answer in either, ✓, ✕ or NA
But for the summary, i need Progress Percentage and also Condition Percentage.
Eg: the question : “Check High Pressure Hydraulic Filter Condition”
Using the if then column for each question.
if the answer ✓ = Progress Percentage is Counted as 1, Condition Percentage is counted as 1 as well,
if the answer ✕ = Progress Percentage is Counted as 1, Condition Percentage is counted as 0.
So in total i have to have 76 x 3 = 228 columns basically ? it is correct?
And that would just be saved in a single column.
Then you use a 76 row Helper Table to manipulate it.
It’s a very effective and efficient technique, but quite complicated to explain.
That’s not the one I was thinking of, but yes that thread will help you understand the Helper Table concept.
Actually, this is a fairly simple use case, and so JSON might be overkill. I guess it depends on whether or not the list of questions would ever change. If they won’t, then all you really need to save is the answers.
So what you could do is create a Questions table, and list all your questions in one column. Then add a User Specific column to capture the answers. Then use a joined list column to create a joined list of all the answers, and save that.
Yes, it would be possible to come back and edit the answers later. Although the logic for that would be a little different. Basically, you’d need to load the RowID of the submitted answer, use a relation + lookup to fetch the joined list of answers, use a split text + single value to expand the answers across all rows, and then go from there.