Hi Hilary, I think I'm giving up on this because I've
thought of a couple of problems with this button approach. Firstly (and for the first instance of the Repeating
Section) you can successfully filter the repeating secondary data source OK once
you click the button - great - however what then becomes clear is that when you
choose an alternative drop-down options which might use a different
OverallLevel number, of course it has the results from that same Keywords List data
source but only has the value of the filtered elements to choose from, and of
course it fails turning the OverallLevel field blank. I overcame that by adding two extra rules
onto the OverallNumber field to reset the filter of Query to blank and re-ran
the Keywords before the calculation.
That fixed it nicely and when I created a second repeating section both
Number and Level fields ran independently and OK. Success.
But. Reverting to
look at the 'Button' at this point, if both OverallLevel numbers in their
respective sections were different, and the button was pressed, it failed so I
took your advice and removed the repeating secondary data source entirely, and
re-added the entire set of fields as a repeating section, just to see what was
happening. I did include a filter on the
section such that if 'Field' is NOT = 'Matrix' then hide and this limited the elements
to just those Keyword options.
However I've identified a black hole I think here which
is that if the value of the fields in total is set correctly by the button,
then unfortunately it doesn’t only affect the 'Icon' field in the repeating
section in which that button resides, it refreshes the values of the Icon
fields for the whole form, and therefore the 'Icon' field in every other
sections also get altered.
Either way, I've decided enough is enough at this
point. Aaarrrgghhh. I've now stopped bashing my head against the
wall and it is great!!!!!
I might revert to a much simpler method I used before which
was to hold the secondary data Keyword images in a number of separate sections
(numbered 1 through 10) and have specific 'hide whens' on each section to reflect the thresholds
directly. This worked but was a clunky
design but so be it.
Thanks very much for all your help.
Alan C.