My app has a repeating group that I am performing a daisy-chain filter on.
The three filters are stored within a reusable element along with a Fuzzy search input.
In the reusable element, I have created custom states that update when one of the multiselect inputs changes. These values can then be accessed from the App page (that part of the daisy-chain filter is working).
I can’t figure out how to reference the Fuzzy Search though.
Do I have to leave the search element on the App page? I tried this but couldn’t get it to work.
I tried a number of things to get this to work, but I think it was a bug that got me going in circles.
I originally copied the Fuzzy Search element from my Reusable into my app page when I was first testing it and it didn’t connect properly.
I had to create a new FS element from scratch and remap the input ID.
I have a custom state in the Reusable that displays the input field and this is used in the conditional to activate the Fuzzy Search.
I’m not sure if this is the most efficient way of doing it.
It works, but feels a little clunky.
I’m trying to design my own daisy chain filtering now, though not with reusables as of yet.
I don’t have any useful thoughts to add but curious how your workaround has held up? Good enough or did you make further changes after more testing/experience?
I’m building a single-page app, so I’m using as many reusable elements as possible to keep it clean. This also helps with reducing the number of workflows on an individual page.
The only issue I have is with the triggers, as the daisy chain won’t start unless triggered.
In my reusable element, I have a yes/no custom state that acts as a trigger.
When any of the filters change, they alternate the Yes/No custom state, this then triggers the daisy chain in my app.
I honestly don’t know if this is the best way of doing it, but for me, it’s keeping the app cleaner and more manageable.
