So…some advice for you is not to make it more complicated than it needs to be.
At the end of the day… you are communicating a story, not articulating the fullest details possible. so Id suggest the following
- decide on the 1-3 examples you would use to demonstrate this filtering feature. (e.g. New York, Miami )
- create 2 dropdown, one for what u want to see for each (and label them eg: +NY, +M) and also create a default dropdown which will appear if neither NY or Mi is selected. and that default dropdown can be visible on load. (unless you want the dropdown to only appear as the selections progress)
- place these dropdown over each other (stacked on the z axis, but both with the same x,y coordinates) on the page, where you want them to appear, and setup an interaction for Loaded>show/Hide>Hide this
- then on the master dropdown, add a case which says if selected option of this dropdown equals New York,> then show +NY, and hide +MI, hide default
- also duplicate that case and adjust it for Miami (if selected option of this dropdown equals Miami > then hide +NY and show +MI., hide default
- to deal with anything else being chosen, you can hide ny, hide mi, show default
since the default, NY, and Mi dropdown are all stacked at the same x,y coordinates, if you do this well, only one will show at a time, giving the ‘illusion’ that your master dropdown is filtering.
pull that off, and you’re well on your way my young illusionist. Remember it’s all smoke and mirrors. your viewers imagination will fill I the blanks and build the story to your brain that it will technically work like they see. ur job here is to make it believable, not to make it operate as it will when actually developed.
The dynamic setdroplist example above is fine, but every time u use a dynamic panel on the page…u ‘load’ your page down…and if you ever create a complex prototype with various states and progressions on a single page… you will feel the hurt on that initial load page. I’ve done some incredibly complex ones (with nearly 200 different states and interactions that felt REAL when run, but took nearly a full minute to load the page). So keeping those for groupings that require timings, or to appear as popups on screen is prolly a better use for that. and in cases like this…a simple show hide interaction should get the job done.
Hope that makes sense.