So, I have this:

In the Assign I'm creating the OrderBy value, so when we get to the break point, the variables used in the aggregate look like this:

If I continue running, the application will crash, with this error:

which doesn't make any sense, because the OrderBy value is perfectly valid.

In fact, if I go back to the Aggregate designer and set the test values exactly like that, it works just fine:


So, anyone have any idea what's happening here?

Thanks!

@Carlos

Are you Grouping By something? Is by any chance one of those columns in the order by out of the aggregation?

forget it

Hi Carlos,

Though I'm not sure what happens, I'm wondering why you titled your question "Another bug in aggregates". Do you experience other bugs as well?

Hi João,

No, I don't have any groups in that aggregate.

In fact, the aggregate is very simple:

Kilian Hekhuis wrote:

Hi Carlos,

Though I'm not sure what happens, I'm wondering why you titled your question "Another bug in aggregates". Do you experience other bugs as well?

Yup:

https://www.outsystems.com/forums/discussion/22169/bug-in-aggregates/

Maybe I'm jinxed, or something!

:)

Hi again!

Have you any case the "order by" expression is void. In the SQL statement normally with a "order by " void you get an error.

Regards

Graça  

Hi Maria,

That's a good point, and I'm being careful not to do that.

My problem is that while the Aggregate does work with the default OrderBy value, as soon as I click a column it stops working. But then, when I try the OrderBy value in the aggregate designer, it works fine.