Sum of all records in a table

[TJJones]

I have run into an issue with a Canvas app using a Dataverse table.

I need to calculate the sum of a records in a table (less than 200). I used the following query for a gallery screen:

AddColumns(GroupBy(Filter(CS_Transfers, 'CS_Transfers (Views)'.'CS_Transfers - Shucks'),"cre07_source","DATA"), "SumTons", Sum(DATA,Tons), "SumLoads", Sum(DATA,LoadSize), "CLoads", Sum(DATA,Contract_ID.Loads)/CountRows(DATA), "CTons", Sum(DATA,Contract_ID.Units)/CountRows(DATA))

This worked fine until we reached about 100 records. Now if that screen is accessed either in run mode or in edit, it locks up and times out with a memory error. I can't even change the query without removing some records from the CS_Transfers table.

I'm fairly new to PowerApps, so if someone has a more efficient way to build a sum for all records, I would really appreciate some ideas.

Thanks,

TJ

[AhmedSalih]

Hello, @TJJones, to get the count of rows in a Dataverse table use this formula:

CountIf(TableName, true)

---

If my reply helped you, please give a 👍 If it solved your issue, please give a 👍 & accept it as the Solution to help other community members find it more.

Visit my Blog: ahmedsalih.blog

Visit my YouTube Channel: https://www.youtube.com/@powerplatformplace/videos

Microsoft Business Application MVP

[FLMike]

Hello,

Lots of thoughts on this and ways to resolve. But may I ask how many rows will you ever have in that table?

My suggestion is to read the data out into a Collection.

Then do you work on the Collection. Don't do the sums, just read the data out, then do your work in the gallery/summing on the collection. I do suggest you only grab the columns you need, not the whole table (if you can reduce it)

I'd have to dig in more if you want to do it differently or if you tell me the table will grow really large.

Cheers
If you like my answer, please Mark it as Resolved, and give it a thumbs up, so it can help others
Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

[MaintenanceGuy]

so when this page opens you are pretty much asking to run all these sums at the same time and crashing the app due to memory failure? If I’m understanding that correctly? I would think break up the sun work with individual requests of sums to lighten the load

[TJJones]

Tried CountIf, but that didn't help. I find it hard to believe that this doesn't work when there are only 114 rows in the table. I don't believe this table will get to be a lot larger.

I can't say for sure that it is a memory issue, but removing the first 35 records, allows it to run again. 

After putting in the CountIf, I started getting an "Invalid operation: division by zero" error. I put some a code to try to resolve that everywhere in that section of the app where division is used. That code didn't fix that issue either. 

I've now changed the code to the following:

AddColumns(GroupBy(Filter(CS_Transfers, 'CS_Transfers (Views)'.'CS_Transfers - Shucks'),"cre07_source","DATA"), "SumTons", Sum(DATA,Tons), "SumLoads", Sum(DATA,LoadSize), "CLoads", IfError(Sum(DATA,Contract_ID.Loads)/CountIf(DATA,true),0), "CTons", IfError(Sum(DATA,Contract_ID.Units)/CountIf(DATA,true),0))

So now if I put the 35 records back in, the app will crash whenever the screen with the report gallery is selected. It doesn't matter if this is by running the app or if editing. Both ways will lock up the app and give an error.  The dots go across the screen for about 60 seconds and the attached error message appears.

It is also funny to me that I have another screen that reads the same table with almost the exact same code and it still works.

I have a ticket in with Microsoft to see if someone can take a closer look to see what is going on.

Thanks to everyone for your suggestions and help.

[TJJones]

I've tried not to use collections in this app due to the fear that some tables might grow beyond 500 rows, but it is possible that I filter by year and type it would prevent there ever being more than 500 rows.

There are only 4 fields being pulled. Tons and Loads from the CS_Transfers table and Loads and Units from the Contracts table via a view and Contract_ID relationship between those two tables. There very few contracts (<20), but I suppose that doing a sum across this could also be a contributing factor. 

[MaintenanceGuy]

just an idea for testing maybe narrow down what part of you function is causing the error. try just doing one section at a time see if one of the sum lines is causing the issue?

[TJJones]

Ok... just so maybe this will help someone else with a similar issue, I will explain what I did to resolve the issue. 

Instead of pulling the sum data into the gallery, I instead do a collection and groupby, loading that OnStart.

ClearCollect(
GroupedItems,
GroupBy(
Filter(CS_Transfers, StartsWith(Product_ID,"CO")),
"cre07_source",
"GroupedColumns"
)
);

ClearCollect(
GroupedItems,
GroupBy(
Filter(CS_Transfers, StartsWith(Product_ID,"SH")),
"cre07_source",
"GroupedColumns"
)
)

The main issue I ran into with this approach is that since the screen calculates values immediately, there were division by zero errors the first time accessing the screen. Loading the lookup at start does not solve the problem. The resolution to that issue was to do an If statement to check if the value was 0 before calculating. If the value is 0 then just display 0 and don't do the division.
Unfortunately, Microsoft never followed up and got back to me, so I was pretty much on my own to figure this out. I will say Bing chat was somewhat helpful but can be really annoying if you don't come at things in the correct way. I had several times where it just kept repeating the same series of answers. Slightly better that a helpdesk person using search, but the AI still needs work.

[FLMike]

To me it was always the best choice,

You were going to need to do too many sums etc and counts separately, then using a Collection. Glad it worked out.