web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Refresh button becomes...
Power Apps
Answered

Refresh button becomes unusable after running SaveData function

(0) ShareShare
ReportReport
Posted on by 258

My app has a few icons that users can tap to get new data. It saves offline copies because sometimes they have to work in areas that have poor/no signal. The code is mostly like this in each one:

 

Concurrent(
 Set(gblLoadingOverlay,true), // 1 - display loading visual
 Refresh('Re-Fueling Logs'); // 2a - refresh SharePoint list
	 ClearCollect(colFuel, // 2b - collect data
 SortByColumns(
 Filter('Re-Fueling Logs',DriverEmail=gblUserProfile.email),
 "DateandTime",
 SortOrder.Descending
 )
 )
);
Set(gblLoadingOverlay,false);
SaveData(colFuel,"colFuelDataFile")

For mobile users, this only works on the first press. After that, the icon becomes unusable. I tried turning off "Auto disable on select", and while that made the icon visually responsive on successive taps, it wouldn't run any of the OnSelect code. Having the SaveData line switch places with the line above it causes it to be stuck on the loading visual for minutes of time even though it clearly isn't doing anything (the trailing dots at the top go away), and placing it after ClearCollect in the Concurrent function has the same effect. The data it's downloading isn't very large either: for the user I'm testing with, it pulls 25 rows from a 251-row table, each row having 30 columns (most of which are blank or hold no data longer than 19 characters). The only thing that fixes the issue is removing SaveData, but that isn't ideal given the use case.

 

What should I do?

Categories:
  • Verified answer
    BCLS776 Profile Picture
    8,994 Moderator on at

    I recommend the following:

    • Remove the Concurrent() function - it is unnecessary for your Filter() to function and may be causing a data conflict
    • Remove the Refresh() - this is a slow reload of all queries to a datasource and is rarely necessary

     

    Hope that helps,

    Bryan

  • bobesponja Profile Picture
    258 on at

    Team ended up removing SaveData, so I guess I won't get to see how this plays out. However, the Concurrent() sadly wasn't removable in some cases because it referenced more than one collection. Refresh() has sometimes been found necessary in apps where we have a refresh timer run every 5 seconds to break around the 35-second throttle limit, but since this one wasn't an auto-refresh, it could've benefitted from it. Will checkmark this just in case it helps someone.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Leaderboard > Power Apps

#1
11manish Profile Picture

11manish 350 Super User 2026 Season 2

#2
M Bilal Khan Profile Picture

M Bilal Khan 318

#3
Mohsin Ali Profile Picture

Mohsin Ali 220

Last 30 days Overall leaderboard