This is really awesome! thank you for explaining (showing slowly) how to add a double lookup! I got this part to work perfectly.
I have really tried searching for an example block that is super simple, to wrap my head around this, but I only seem to find examples of pretty complicated blocks where others are either having trouble, or the block complexity is outside of my knowledge scope.
Is there a simple example block anywhere that I might be able to use to help me figure this out?
Typically, I use Visibility states for every option I think I will need, but I think we can all agree that these can get out of hand when you have too many visibilities.
I've started using Lookups to help me add options, but I typically just drive these from the visibility states. This creates a grip for anything I usually want to change.
With a double lookup, should you be able to pick from two different data sets from the grip?
When I add a Double lookup, I don't seem to have the ability to choose the info I have used to drive the table.
A simple example could really help me out.
Attached is a block that I would like to keep the visibilities limited to what I have, but be able to have a lookup table that pulls from a "list" that isn't really an action.
For example:
if the Visibility Grip is set to "Sealant And Backer Rod"
Is there a way to get the Lookup Grip "Manufacturer" (and others) so that it pulls from a "list" somehow and not from an Action parameter? A list that has all our venders on it, for example?
Am I barking up the wrong tree here?
Thank you all so much!!