Hi Dorine, So I need to have 2 aggregates now one for the table and the other to be filtered (assuming because it is not linked to a table it will bring back all records)?

Well, I can't answer that without understanding what you are trying to achieve.  

Why do you do the filtering ? just to know the number of records that are completed for example ??  In that case, yes, probably having a separate aggregate for counting this would be more useful than retrieving everything, and then filtering.

So can you tell us more about why you do the filtering ?

Yes, the filtered values are for counters above the table. to show how many records are open and complete.
So would you have 1 aggregate (and filter that using the filter list actions as I did) or bring 2 additional aggregates (if I have a counter for complete and another for open without using the list filter action)?


Regardless of using 1 or 2 additional aggregates this sounds like duplication.
I am now bringing the 50 records for the table + at least 63 records (for the counters). When I could just bring 63 records overall.
I guess I never knew Outsystems automatically tried to predict what I was using the aggregate for and depending on that would make the decision to send all or some values. Maybe they should optimise this if the aggregate is being used by filterlist actions (or any other type of list action) then bring all the records...

This creates a maintenance issue as well if I change my aggregate in the future then I need to change it twice or 3 times...

I guess I could optimise this by creating a get action and then using this for the table and the filterslist actions.

So yes, you are asking all the right questions :-)

And your choice will really depend on things like performance, and indeed duplication in case of more complex queries.

But honestly, i think knowing the count in the database of some items with a given status, is a completely different requirement than bringing back a list to show to the user.  What if you would like to start adding search or filter options for the user on the list, at that point, you wouldn't be able to do some after the fact filters on the aggregate result to do your counting either, could you.

I personally would probably separate these needs into separate queries / aggregates.   And in your case, if you want to count both completed and open, I would imagine one aggregate with a group by on status, this will give you all your counts, and a separate aggregate to bring back the 50 records to show.

Dorine