My form is for running software tests. View 1 is where the configuration information is entered, view 2 is a series of sections with a test plan for each possible test (and the irrelevant tests get hidden as the configuration options are marked), view 3 is the result summary where I have the repeating table I'm working with.
On the test plan page, I have several sections with other repeating tables that point to the data that was entered on the first page (so that the tester doesn't have to flip back and forth to see what was entered), but then I also have extra fields for Expected Result, Actual Result, and Pass/Qualified Pass/Fail (these latter are option buttons).
The result summary basically takes counts of all the Pass/Qualified Passes/Fails to get the total number of tests, but it's in the test plan sections themselves that I separately calculate the number of Passes, Qualified Passes, Fails and run percentages where % Passes = # Passes/# Tests, % Qual Passes = # Qual Passes/# Tests and %Fails = # Fails/# Tests. Each row number in the repeating table I'm trying to build on the Summary page corresponds to the results for one of the tests on the Test Plan page.
So the counts are based on different option button controls in different sections - and the only way to get a consistent formula would be to use row numbers, something like
For i = 1 to 14
PctPasses(row i) = Total Passes(row i) / Total Tests (row i)
PctQPs(row i) = Total QPs(row i) / Total Tests (row i)
PctFails (row i) - Total Fails (row i) / Total Tests (row i)
Next i
Except I don't want to have to do custom code if I can avoid it.
I actually have a separate table set up that is not a repeating table that does all the calculations manually, but with 14 rows, that's more than 100 controls in just that table. I was just hoping to be able to use a repeating table so I could use row-based conditional formatting to hide rows that correspond to tests that weren't run. On the non-repeating table, I have some conditional formatting that grays out the fields on rows that have tests that weren't run, but it's not very pretty.
FYI, I tried using qRules to apply a filter to the field to be updated to see if I could update only a particular row, but once again it applies whatever changes I make to every column in the table. <sigh> I have a mini-mockup of the repeating table I'm trying to build (minus all the counts/calculations) if you want to look at it. At this point, I've built a repeating table like the one I want to build for the result summary and I'm only trying to see if I can use qRules SetValue to update only one row in the repeating table. If you think it would be helpful to see the mockup, let me know and I'll post it.
Does this help? And sorry for the delay in responding - I've been called off to work on other things and have posted a few other questions here in the meantime.
Thanks,
Natalie (nkstrou)
An imprecisely defined requirement has an infinite number of possible solutions. Unfortunately, only about a maxiumum of 3 solutions are actually satisfactory to the end user.