Hello Mykola,

I believe that, if you don't specify, either it will return every record or will only return a given number tied to the "display widget" - like a table records or so.

If you put 0, seems that returning 1 is "fallback" behavior since, if you don't need any record then you don't need an aggregate.

Cheers!

Hello Armando,

I've had that thought also but in this case I have a variable with a list type that is displayed with table records widget  (with line count set to list length) and aggregate result list is assigned to this variable. 

Regarding fallback for 0 it can be used for testing purpose or another reason and as it is not mentioned in the aggregate description nor in the max.records field this behavior was unexpected (

Hi guys, I had the exactly same behavior that Mykola described, I also use a List binded to a table with the line count set to this list length and had only 50 elements shown.

this is totally unexpected, the only work around I found was to set max records for a huge number in aggregate.

This seems like something still wrong!

You can create there in Site Properties, a variable of type integer and put the value you wantEx: MaxRecord,and in your application call this variable, with the following writing:Site.MaxRecordIt ends up being the same thing you did, but it's good to be careful about putting high numbers, because there will be many requests that the application will have to validate. As a good practice, you can use the aggregates to search in a more consolidated way, and if you have to display the analytical data, it will be on a controlled amount and without forcing so many requests.