@Grant Sorry I didn’t see this earlier. I thought this would send an email, but that’s another topic…
The variable is HTTP (REST), not SQL. But I get your idea, that I could use inputs and parameters.
Exactly. A relatively small amount of data can still be huge list to scroll through. So active filtering would be great.
To do this with constant API calls, it can take a few seconds for the round trip, which adds up if you aren’t a robot who goes directly to the data it needs, but rather you poke around a bit till you get the right job number or whatever.