Expression Editor Creates Wrong Condition With a Count Aggregate In Server Step

Wappler 2.8.3 Windows 10

New expression editor is creating the wrong expression… here is my database query alias for price_count:

nob1

and here is the equation created from it:

nob

Which should read:

fetch_from_prices[0].price_count > 0

Am finding it confusing as to which I select here in order to create the greater than operation… the expression or the ‘0’:

nob2

And in fiddling around to make this post, I just managed to create this strange expression:

nob3

Haven’t gone to 2.8.4 yet… is this issue better in the latest release?

Can you show a short video how are you doing this and where exactly as it’s not really clear from your screenshots …

Here is the video below.

Have just turned off experimental, and the same thing is happening in the old expression editor too!

It seems to be when you have a multi-record query and you have a count aggregation… like this:

Database query get_my_count:
SELECT COUNT (id) AS my_count FROM table_name WHERE condition;

Then you want to test:

get_my_count[0].my_count > 0

And Wappler writes the condition as:

get_my_count.my_count0 > 0

It doesn’t matter if you have the new expression editor or not!

1 Like

Thanks, all clear now.
@George will check it

2 Likes