Wappler Version : 3.5.1
Operating System : mac / node
Expected behavior
Fields from a paged query should be selectable
Actual behavior
Only the data array is shown
How to reproduce
Paged Records (invalid)
Multiple Records (valid)
Hi Ken, where do you see these - which dialog is this?
So it’s the picker for the condition expression in server connect?
But if that’s a multi results query, you will need to put it in a repeat to be able to pick it’s columns.
Or do I not understand what exactly are you trying to do?
Correct, the expression.
Why would it work for multiple query, but not paged?
An example of the need, a condition that uses join.
But what exactly do you want to check / use as an expression in the condition?
@George will check this. For multiple query it will just show the columns but will select the first one only.
It really depends on what exactly are you trying to check/use?
Sorry Teodor, this is where you lose my interest.
I’ve reported a bug, if you guys don’t feel it’s a bug, then that’s that.
For now, I’ll just manually type in what I want.
Thanks for taking a look!
I am trying to understand what this query contains and what property are you trying to access so I can recreate this locally.
You mentioned some joins, so I am asking - what exactly do you need to use as an expression there?
I’ll post that up once I manually figure it out…I’m currently faced with another issue with db connection breaking when Wappler updated some files.
Just as a background info we had two types of data pickers, one that you see now with all the steps and one that we had for a bit that shows only output data.
My preference goes to implementing the one with output data only as it was much clearer, but we had to revert it a while ago because it had some issues with nested conditional output.
Once we fix that we will put it back.
Then you will be able to open arrays and explore their inners
On the surface, this sounds bad to me...I've had plenty of situations where I could not select data, just because the output option was not ticked. I don't understand that. Output should be completely bifurcated from whether or not something is shown in a picker. I use values all the time that do not require output.
Sorry I wasn’t very clear - I ment the step data only, not the just the output.
The datapicker within server connect displays all the data of the previous steps no matter if output is selected or not.
In app connect - there you can see indeed only the server connect data that has been enabled for output.
1 Like
This has been fixed in Wappler 3.7.4
This topic was automatically closed after 46 hours. New replies are no longer allowed.