The field is there. In fact the query runs, but it no longer sorts by the aggregate field - well it does, but by an additional field which of course means the sort order is incorrect.
The change I made was to add the aggregate (count) field manually, here:
. and that worked. Now it doesn’t - [quote=“nshkrsh, post:17, topic:13025, full:true”]
that warning looks like in DB you do not have that field any more.
and it shouldn’t look like that. it should look proper like a modal - not all curled up.
an additional field is added to the ORDER BY statement, perhaps because Wappler doesn’t recognise the field I added, so it includes what it considers a valid value. I imagine another result of not recognising the field is the broken query builder display.
In any case, it would be really good if this were fixed. It’s one of those strange issues which is potentially a serious omission, but hasn’t been acknowledged or commented on by the Wappler team (AFAIK).