Unanswered

Powerapps very slow to patch to sharepoint list

(2) Share

Report

Posted on by mohaimen88

Hi All,

I'm building a timesheet app for my company and facing a delay/latency issue with submitting to sharepoint list. here's how my app is built:

1. I'm pulling a full list of workers names, IDs, etc from a sharepoint list to a collection

2. using a gallery to update the collection with regular hours/overtime and presence status for each worker.

3. a save button with patch command to patch the collection to a sharepoint list.

the problem I'm facing is the app is taking 2-5 min to submit the collection (about 50 lines), and if the user exit the app before it finishes uploading the data, the process will not complete... Please help. thank you

Mo.

Categories:

Building Power Apps

I have the same question (0)

All responses (8)

Answers (0)

v-xida-msft on at

Like (0)

Report
Hi @mohaimen88 ,

Could you please share more details about the formula you used in your app to patch collection to your SP List?

Actually, there are many reasons that an app can be slow to load, slow to respond, and slow to write to data sources. Please check the performace suggestions in the following blog:

https://baizini-it.com/blog/index.php/2017/09/13/powerapps-improving-app-performance/

If you want to patch a collection back to your SP List, the standard formula as below:

ForAll( Collection1, Patch( 'YourSPList', LookUp('YourSPList', ID = Collection1[@ID]), { Column1: Collection1[@Column1], Column2: Collection1[@Column2], Column3: Collection1[@Column3], ... } ) )

In addition, please mak sure the Network on your side is in a good condition and the available RAM is enough on your PC. The Network state and available RAM would also affect the data process in your app.

Please also check if the following performance tips for canvas app would help in your scenario:

https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/performance-tips

Best regards,

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report
Thank you Kris, I tried the threads you sent with no luck.

here's the formula I'm using:
ForAll(ColLabor, Patch(TS_LIST, Defaults(TS_LIST), { TS_LABORNAME: L_LaborName, TS_LABORNUM: L_LaborNumber, TS_PROF: L_Prof, TS_PROJECT: L_Project, TS_REGHOURS: L_Hours, TS_OTHOURS: L_OT, TS_HOLIDAYHOURS: L_Holiday, TS_REMARKS: L_Remarks, TS_DATE: F_Date.SelectedDate, TS_CreatedBy: DD_CreatedBy.Selected.Title, TS_ABSENT: L_Absent })),

Thank you
Mo

Was this reply helpful? Yes No
Drrickryp Super User 2024 Season 1 on at

Like (0)

Report

Was this reply helpful? Yes No
pchettri 39 on at

Like (0)

Report

any soloution ? even i am facing the same issue, when i patch using
ForAll(
Collection,
Patch(
Source,
Defaults(Source),
{
ABC: VarStaffId})) Note: my collection is gallery.allitems

Was this reply helpful? Yes No
DonPepe 24 on at

Like (0)

Report

Same issue on my side.
I need to update a unique record (single line of 80 columns) and it takes like 5 to 10 minutes to update.
It's crazy because it's not that much data, it should be instantaneous.

Was this reply helpful? Yes No
DonPepe 24 on at

Like (0)

Report

Hi @mohaimen88 try to split your patch in several patch.
Like from this :
Patch(YourListSharepoint; LookUp(YourListSharepoint;ID=id); { field_1: ...; field_2: ...; field_3: ...; field_4: ....})
To this :
Patch(YourListSharepoint; LookUp(YourListSharepoint;ID=id); { field_1: ...; field_2: ...})
Patch(YourListSharepoint; LookUp(YourListSharepoint;ID=id); { field_3: ...; field_4: ....})

Don't know why it works better but on my side it's the case.

Kr,

Don

Was this reply helpful? Yes No
Suggested answer

CU07100307-0 2 on at

Like (0)

Report

Patch(

YourTable,

ForAll(

     YourCollection As Record,

     {

         column1: Record.collectionColumn1,

         .....

     }

)

)

Try this way, it will speed up your problem. But this way don't patch row by row, please check your database before doing your next step.

Was this reply helpful? Yes No
WarrenBelz 153,042 Most Valuable Professional on at

Like (1)

Report
This is an old post, but for the record, the reason is that if you use Patch inside a ForAll statement, then PowerApps "loops through" the collection and does an individual Patch for each record in the collection. This is inefficient and can be slow if the collection has a bigger number of records. ForAll() produces a Table, which you can construct and then send to SharePoint in one Patch, which is far more efficient and quicker.
Patch( TS_LIST, ForAll( ColLabor As _Data, { TS_LABORNAME: _Data.L_LaborName, TS_LABORNUM: _Data.L_LaborNumber, TS_PROF: _Data.L_Prof, TS_PROJECT: _Data.L_Project, TS_REGHOURS: _Data.L_Hours, TS_OTHOURS: _Data.L_OT, TS_HOLIDAYHOURS: _Data.L_Holiday, TS_REMARKS: _Data.L_Remarks, TS_DATE: _F_Date.SelectedDate, TS_CreatedBy: DD_CreatedBy.Selected.Title, TS_ABSENT: _Data.L_Absent } ) )

1 people found this reply helpful.

Was this reply helpful? Yes No