Wappler Version : 5.2.1
Operating System : win 11
Server Model: node
Database Type: SQLite
Hosting Type: wappler node local
What do you think should happen?
results from custom query should be accessible at other stages of API action
What actually happens?
Results from query are not accessible in later stages
While i can see the output in the picker and select it, the value is not actually passed making it unusable
See video
custom query - resutls issue
Stupid me, since the introduction of single queries I completely forgot that with a normal query, even if only one result, you still need to use a repeat to access the values in the query.
doing this solved it.
The correct expression in the set value step should be {{query1[0].fpq_id}} in order to get the record from the custom query.
Guess it is so long since i have user a multiple query for a single result i forgot the basics where an array reference or repeat is needed in all cases for a multiple record query 
think i am working too hard, need another holiday!
It properly returns the expression for the regular multi records query, but i am not sure how should it handle the custom query results. @George will check this.