XML Tag "Sum" of tree view doesn't sum when there are a lot of records

[Fabyc]

When in a tree view is used the XML tag "Sum", it works perfectly when 

there are not many records for example 50. When in the list the are for 

example 200 or more records, the sum doesn't work [1].

Is it needed to do something else or is it a bug?

[1] https://s31.postimg.org/wmmttpjy3/tag_sum_doesnt_work.png

Thanks

--

Regards

[Cédric Krier]

On 2016-07-29 17:13, Fabyc wrote:
> When in a tree view is used the XML tag "Sum", it works perfectly when
> there are not many records for example 50. When in the list the are for
> example 200 or more records, the sum doesn't work [1].
>
> Is it needed to do something else or is it a bug?

It is the expected behaviour. It is the client who does the sum and so
he needs to have read all the records. But the client is optimized to
limit the number of records it loads for performance reason and the sum
code does not force the client read all the records also for performance
reason.
So if you want to have the sum you must scroll over all the record to
ensure they are all loaded.

There are two possible improvements:

- compute the sum of selected if at least those records are loaded

- defer the sum computation to the server side if records are not
loaded

--
Cédric Krier - B2CK SPRL
Email/Jabber: cedric...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/

[Fabián]

On Sat, Jul 30, 2016 at 4:18 AM, Cédric Krier <cedric...@b2ck.com> wrote:

On 2016-07-29 17:13, Fabyc wrote:
> When in a tree view is used the XML tag "Sum", it works perfectly when
> there are not many records for example 50. When in the list the are for
> example 200 or more records, the sum doesn't work [1].
>
> Is it needed to do something else or is it a bug?

It is the expected behaviour. It is the client who does the sum and so
he needs to have read all the records. But the client is optimized to
limit the number of records it loads for performance reason and the sum
code does not force the client read all the records also for performance
reason.
So if you want to have the sum you must scroll over all the record to
ensure they are all loaded.

OK

 

There are two possible improvements:

    - compute the sum of selected if at least those records are loaded

    - defer the sum computation to the server side if records are not
      loaded

+1

Very good improvements.

Thanks

--

Regards

Fabyc