taking long time to patch records

(0) Share

Report

Posted on by Cewolf

Greetings All,

I have a fast Q, we have an application that would patch records from a collection to a Onedrive Excel table.

some of the users experienced loooooong upload times once they have 30+ records to patch. (up to 12 mins and some claimed and hour)

the collection has basic fields like name, project, activity, count, date etc. (text, number, date) nothing fancy.

I thought to Concat/Concatenate the records into one field to see if that improve the patch time, but didn't seem to help.

any one experienced something like that and/or knows how it can be solved ?

thanks a lot.

PS: The users are working in a factory and don't have internet coverage and thus need to come to the office at the end of day to upload their records.

Categories:

Building Power Apps

All responses (6)

Answers (1)

Sort by

WarrenBelz 156,576 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Cewolf ,
How many users are on the app concurrently? The performance of Excel-based data degrades considerably as more users access it. You should seriously consider moving to a SharePoint data source if this continues to be an issue.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
Cewolf 8 on at

Like
a
(0)

Report
Copy link

Link copied!

Max Users are 8 , but they don't upload in the same time,
at the beginning it was stored on SharePoint but I had to move it to Excel for better editing the data, since the list will contain thousands of records and SharePoint is limited to view 5000 records max, plus it is tedious to try to edit or clean up data there !!
The application just patched new records, it does not read from there.
Verified answer

WarrenBelz 156,576 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

@Cewolf ,
Excel is worse at large data sets - have a read of this article - and was never really designed (in my opinion anyway) for anything other than reference lists. The 5,000 item view limit in SharePoint can be easily managed with Filters in views (I have some lists with 30,000+ records) and the DataSheet/Quick Edit function is just as good if not better than Excel for editing (which you cannot have open while anyone in Power App is connected to it).
Excel performance is what it is - there is really no code in Power Apps that can make it any different - I would urge you to return to SharePoint.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
Cewolf 8 on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks a lot for your reply ,
I came across this article while I was deciding where to store the data ...
at the end I decided to go with Excel for 2 reasons, our staff are more comfortable with Excel in case they needed to correct some records and asking them to use SharePoint will face some resistance.
the second reason and the most important is that I am using the same Excel file for reporting, pivot tables and performance charts.
It is not possible to use PowerApps with the 2000 record limit, plus our staff does not have licence to Power BI so power BI is out of the question.
basically I am looking for the least of the 7 evils !! 😁

I came across a solution, (more like walking around than solution), I applied "Concat" to the entire Collection into one Cell and Patch it... dropped time for the test sample from one min to 20 sec. Then using some of power query wizardry, I change them back into records in their original tabular format.

I am still considering SharePoint as a data source and then use an Excel file to convert them into reports and charts. but the concat option was still faster that using SharePoint ...

Any other thoughts/ideas/recommendations !!
WarrenBelz 156,576 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks @Cewolf ,i
I will throw one more thing in (as I use it) - a SharePoint view exports directly into a downloaded Excel file in the top menu and can then be pasted into any Excel reporting template tab you set up for the purpose. You do not have to suffer the limitations of Excel as a data source if reporting is the only barrier.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
Cewolf 8 on at

Like
a
(0)

Report
Copy link

Link copied!

Here is a summary of performance
For a collection of 40 records

Patch to Excel File: 7:21 min
Patch to SharePoint: 0:43 min
Concat and Patch to Excel: 0:13 min
Concat and Patch to SharePoint: 0:03 min

Guess we are back to SharePoint .

thanks all for you help