Client-Side Summary Compute Help

[mikeallenbrown]

Web app running 5159-5132.

In a list control I'm utilizing the "Compute summary values" method. I now have a need to only compute specific rows based on a value in the same row.

I have this currently in the list control's afterClientSideSummaryCompute...

var _paid = csSummary['Amount'].total;

That sums up the "Amount" column well enough but I only want "completed" rows (field name is called status) to be summed up.

[jgrannis]

Re: Client-Side Summary Compute Help

You will not need "Compute summary values" nor afterClientSideSummaryCompute.
In the list's onListDraw event, you could add:

var _paid = data.reduce((total, data) => {if(data.Status == 'Completed') {total + data.Amount}; return data.Amount},0);

[mikeallenbrown]

Re: Client-Side Summary Compute Help

Thanks for responding, Jeff.

I get this error however: Uncaught TypeError: data.reduce is not a function

I used the below code. Only difference is variable name and "SUBMITTED" instead of "COMPLETED".

var _out = data.reduce((total, data) => {if(data.Status == 'SUBMITTED') {total + data.Amount}; return data.Amount},0);

[mikeallenbrown]

Re: Client-Side Summary Compute Help

Test case attached. I would expect the alert to say 150 but it says 25.


list_Test.a5wcmp

[jgrannis]

Re: Client-Side Summary Compute Help

I suppose reduce isn't supported by some older browsers but I thought they had to be really quite old.

Also, perhaps you'll need to use Number(data.Amount)

[mikeallenbrown]

Re: Client-Side Summary Compute Help

Ran this in Google's Chrome browser. It's up to date.

I'll try Number(data.Amount).

[jgrannis]

Re: Client-Side Summary Compute Help

I just tested it out more... What I gave you might not be quite right. I'm still looking at it.

[jgrannis]

Re: Client-Side Summary Compute Help

Ok, this is better:

var _out = data.filter((data) => data.Status === 'SUBMITTED').map((data) => Number(data.Amount)).reduce((total, data) => total + data);

[mikeallenbrown]

Re: Client-Side Summary Compute Help

That works for my test case list in post #4. Thank you. It's appreciated.

Doesn't work in my actual list I am using. Now it says Uncaught TypeError: data.filter is not a function. Clearly something is conflicting with this in my list. I have a lot going on in it. Will have to track down the cultriate. At least I have something to go with noe. Thanks again.

[jgrannis]

Re: Client-Side Summary Compute Help

On my side I was copying from
different places (list events) and was getting mixed up with scope (data from just one row versus list data).
If you haven’t done it already, maybe just trying outside any list event, to get the list’s _rData and with that array trying out the chained “filter,map,reduce”

[mikeallenbrown]

Re: Client-Side Summary Compute Help

Thanks, I'll give it a shot.

[frankbicknell]

Re: Client-Side Summary Compute Help

Could you do it with a view and a little logic,
Or even in the sql statement of the list?

[mikeallenbrown]

Re: Client-Side Summary Compute Help

Thanks for the suggestion, Frank. I think that is the very route I am going to take.

[Davidk]

Re: Client-Side Summary Compute Help

Try this in your onListDraw event...

function getSum(total, data) {
	if(data.Status == 'COMPLETED'){
    	return total + data.Amount;
    }else{
    	return total + 0;
    }
}
	
var _paid = data.reduce(getSum,0);

alert(_paid);

Remember that case matters... so your Status field would be "Status" and a possible value of "Status" would be "COMPLETED"... and amount would be "Amount".

This has been tested in 5159. By the way, your sample UX has no code in it, no summary value setup, and no Amount or Status in the List static data.

[mikeallenbrown]

Re: Client-Side Summary Compute Help

By the way, your sample UX has no code in it, no summary value setup, and no Amount or Status in the List static data.

Yeah, bad example of a test case. The product of me rushing.

Thanks for the code. I ended up handling my need in SQL. Nonetheless, I've learned some new JS that I am sure will be useful in the future.