Hi Doug.
Thanks for the response. My example doesn't perform the way i want it to at all. If I select a state, in the third list I want a list of all the cities in that state. this works. but, when I narrow the search by selecting a county. I want the cities list to only show the cities present in that county. This does not work as the third list is still showing all the cities in the state, which allows users to make a selection which makes no sense. i.e. they can say that they stay within a city that is not within the correct county.
This is a simplified example for testing purposes.
The actual use case is for a marine invertebrate survey where we have approx 500 species that need to be collected.
The issue is that the field workers having varying understanding about the taxonomy, so there needs to be a case where they can select the species using its common name and scrolling through a list of 500 common names is not ideal.
From a usability perspective. it would be better to have the list of common names to be constrained off varying levels in the taxonomy. so if someone is reasonably certain that the organism belongs in a certain family, they can select a phylum, then a class, then an order and then the family and get a list of common species name in that family. however if they are only capable of narrowing the list by selecting a phylum then the list should also return all the common names of organisms that are within that phylum.
So this is why I need the third list to be constrained off either the first list, or off the second list.
I have just done some reading on the pulldata function. I am not sure how that is applicable in this use case?
Kind Regards
Hayden
