Total beginner here. I have this functioning finally, but the way I got it to work is surely not ideal.
In the app there are dropdown menus to refine the dates/data you want to view:
All gives you all data.
Yearly would make so that your Year dropdown below is what defines the date range.
Monthly would make it so that the Year and the Month dropdowns define the date range.
(I am thinking of changing this to a Tabbed Container or Cascader for better UI )
Each dropdown selection triggers a new state for its corresponding variable (not sure I needed a variable as middle man before passing along, but that's how I got it to work). So I need to pass these selections/stored variable states into my Workflow. I did it like this:
So then into the Workflow, I call them in a sql query like this:
Is this the standard/ideal approach? I saw another post here that didn't even mention using the startTrigger method to access data passed from the app to a workflow.
Using startTrigger.data is a totally valid approach and we see this pattern across many workflows. An alternative is that you can have a block named 'params' where you validate that the data from the startTrigger is as you expect, and then subsequently use params.data in the rest of your workflow.
