Answered

Having issue with Powerapps

(0) Share

Report

Posted on by CU23050719-3

Hi Community,
I am working on a Canvas App connected to a SharePoint list. I am using the Patch() function to update records from an Edit Form.
The record updates successfully in the SharePoint list, but the Gallery connected to the same list does not refresh immediately after the Patch() operation. Users need to manually refresh the app or navigate away and come back to see the updated data.
Current formula:
Patch(
    EmployeeRequests,
    LookUp(EmployeeRequests, ID = SelectedID),
    {
        Status: "Approved"
    }
);
I also tried using:
Refresh(EmployeeRequests)
after the Patch() function, but the gallery still sometimes shows old values.
Environment:
• Power Apps Canvas App
• SharePoint Online list as data source
• Gallery connected directly to the SharePoint list
Questions:
1. Is there a better way to force the gallery to refresh after Patch()?
2. Should I use collections instead of direct SharePoint connection?
3. Are there any delegation or caching limitations causing this behavior?
Any suggestions would be appreciated.
Thanks!

Categories:

General topics

I have the same question (0)

All responses (5)

Answers (2)

Sort by

Suggested answer

Vish WR 3,748 on at

Like
a
(0)

Report
Copy link

Link copied!

@CU23050719-3

This is a known SharePoint connector caching behaviour in Canvas Apps. Even though the Patch succeeds, the gallery holds onto stale data until the datasource is fully re-evaluated.First thing to try — add Reset(Gallery1) after your Refresh() call

try — add Reset(Gallery1) after your Refresh() call:

Patch(
EmployeeRequests,
LookUp(EmployeeRequests, ID = SelectedID),
{ Status: "Approved" }
);
Refresh(EmployeeRequests);
Reset(Gallery1);

Also, confirm your gallery Items property is pointing directly to EmployeeRequests and not to a filtered variable or old collection that isn't getting updated.

If the inconsistency continues, switching to a local collection is the most reliable approach with SharePoint as a datasource:

Patch(
EmployeeRequests,
LookUp(EmployeeRequests, ID = SelectedID),
{ Status: "Approved" }
);
Refresh(EmployeeRequests);
ClearCollect(colRequests, EmployeeRequests);

Then set your gallery Items to colRequests. The gallery now reads from memory instead of waiting on the SharePoint connector, so updates appear instantly every time.

On your delegation question yes, SharePoint connector caching and delegation limits on large lists can contribute to this, especially if you have filters or sorts on the gallery. Using a collection sidesteps most of that.

Vishnu WR

LinkedIn - My Tech Space

Please ✅ Does this answer your question 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 answering Yes to Was this reply helpful? or give it a Like ♥

Was this reply helpful? Yes No
Suggested answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!
Your Patch() logic is correct.

The issue is not the update itself — it is the way Power Apps handles SharePoint datasource caching and Gallery rendering.

Refresh(EmployeeRequests) alone is often unreliable for immediate UI updates because:

SharePoint sync is asynchronous

the Gallery may still hold cached records

Power Apps does not always instantly re-query the datasource.

The most reliable and recommended pattern is:

SharePoint = backend storage

Collection = UI datasource

Patch both backend and collection together

This is the standard production-grade approach for Canvas Apps using SharePoint.

Was this reply helpful? Yes No
Suggested answer

Kalathiya 2,456 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!
Hello @CU23050719-3,

Using a collection alone may not solve the issue because the collection also reloads data from the same SharePoint list. If SharePoint or Power Apps is still returning cached data immediately after Patch(), the collection can also contain old values.

Better approach is to update the gallery source locally after Patch.

Patch(EmployeeRequests, LookUp(EmployeeRequests, ID = SelectedID), { Status: "Approved" } ); Refresh(EmployeeRequests);

The issue is caused by Power Apps caching rather than SharePoint itself. Please try to login with different browser and try it.

Also, display the items in descending order in the Gallery so you can easily verify whether the latest data is being shown or not.

---------------------------------------------------------------------------------
📩 Need more help? Just mention @Kalathiya and I’ll be happy to assist.
✔️ If this answer helped you, please tick “Does this answer your question?” so it can be marked as the Verified Answer.
💛 A Like always motivates me to keep contributing!

Was this reply helpful? Yes No
Verified answer

Nanit Khanna 68 on at

Like
a
(1)

Report
Copy link

Link copied!
Hi,

This is usually caused by SharePoint caching/sync delay in Canvas Apps.

Recommended approach:
• Use:

Patch(...); Refresh(EmployeeRequests); Reset(Gallery1)

• If using a form:

SubmitForm(EditForm1); Refresh(EmployeeRequests)

Best practices:
• Collections can improve UI responsiveness for large lists
• Avoid relying only on direct SharePoint refresh for instant UI updates
• You can also update a local collection after Patch() for immediate gallery changes

Example:

Patch(...); Refresh(EmployeeRequests); ClearCollect(colRequests, EmployeeRequests)

Yes, SharePoint connector caching and delegation behavior can sometimes delay gallery updates briefly after Patch().

Was this reply helpful? Yes No
Verified answer

deepakmehta13a 369 on at

Like
a
(1)

Report
Copy link

Link copied!
Hi,

Patch() updates the SharePoint item correctly, but the Gallery may still show cached data for a short time.

You can try this pattern:

Patch( EmployeeRequests, LookUp(EmployeeRequests, ID = SelectedID), { Status: "Approved" } ); Refresh(EmployeeRequests); Gallery1.Selected

Other suggestions:
• Rebind the Gallery Items property if using filters/sorting
• Use a local collection for better real-time UI updates
• Large SharePoint lists can sometimes delay refresh synchronization

A common approach is:

Refresh(EmployeeRequests); ClearCollect(colRequests, EmployeeRequests)

Then bind the Gallery to colRequests instead of the SharePoint list directly.

If this helps resolve your issue, please consider marking the response as Verified so it can help others facing a similar scenario.

If you found this helpful, you can also click “Yes” on “Was this reply helpful?” or give it a Like.

Was this reply helpful? Yes No