Note: I was required to create an external SQL database in order to accomplish what was discussed here. The database was created about 6 months after asking this question and the feature set was "fully" implemented about 10 months later.
I need to create a drop down list that references the repeating section it is part of. That reference will act as a filter for another drop down list.
It seems that there is a "context node" issue with this functionality. The "master" drop down in Section 2 only lists "Section 2"; the "master" drop down in Section 3 only lists "Section 3". I need all sections to be available in the listing.
Here is a link to an example XSN file which demonstrates this. Please let me know if the link does not work; I've rarely used this host.
The goal is that the first drop down selects the "master" repeating section, the second drop down is then filtered to target the sub-repeating section housed within it.
A simple analogy might be a form that has vehicle makes / models. There are multiple manufacturers, each one with multiple models. I want to be able to add both new makes and models but also reference old makes and models to apply changes etc.
Let me add some example pictures to this...
If I create a drop down list "outside" of the repeating section it works perfectly - here is the data structure and location of the "Selector Drop Down Source":
Here are the options in that selector when two sections have been added:
Now we move the selector location into the repeating table. I am not changing the data source at all:
Now note the available options for the selector drop down when it is embedded in Section 2:
Only that section can be selected! The data source is the same, only the location of the control has changed. Why does this occur? In section 1 only "Section 1" can be selected...