Unanswered

The refresh function in my apps suddenly need to be clicked 2-3x before it actually refreshes

(0) Share

Report

Posted on by kkawtoski

The Refresh(Source) function a few weeks/months ago changed, and I have no idea why. When I click an icon that set to OnClick Refresh(Source), it used to work on the first click. Now, it must be clicked at least twice, sometimes 3 times. This has caused many issues. Did powerapps change something internally? This has wrecked the ability to save items properly because the users don't know when the sources have been refreshed.

Categories:

Building Power Apps

All responses (8)

Answers (0)

Sort by

RandyHayes 76,299 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@kkawtoski

In general, you should not be refreshing your datasources unless there are chances that external users or processes are changing values that you need current in your app.

That aside...are you sure that it is not refreshing? What sign within the app do you see that indicates to you that it is not refreshing?
kkawtoski 22 on at

Like
a
(0)

Report
Copy link

Link copied!

The external users directly change the datasources, so it's necessary to refresh. I am 100% positive it does not refresh. The dots at the top of the screen indicate that it refreshes. Everytime I refresh, it indeed shows the dots, so it looks like it refreshes. But, when I select a gallery item, the data that was input and saved before the refresh is not there. I must back out, refresh 1-2x more, then select the item again and the data is there.
PaulD1 2,914 on at

Like
a
(0)

Report
Copy link

Link copied!

Try turning on the performance monitor to get a better idea of what is really happening (left hand navigator, tools icon, performance monitor). This helps to see much more clearly what data calls your App is actually making.

There are appear to be some 'hidden behaviours' to try to improve performance (or the appearance of performance) - e.g. if you run a 'data request' (e.g. a filter with specific parameters) and then attempt to run exactly the same 'data request' within 30 seconds, it is ignored (at least, that is what I have observed).

That said, Refresh is supposed to always force new requests, but has the undesirable effect of pulling all data for the refreshed data source up to the delegable limit (even if all your formulas referencing the data source are delegable) which is why refresh is such a performance hog.

I suspect the above behaviours are tweaked from time to time by MS, so Performance Monitor is your best bet to see what is really going on.
RandyHayes 76,299 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@kkawtoski

Are you using variables or collections in your app? This sounds like a case of them not being reloaded.
kkawtoski 22 on at

Like
a
(0)

Report
Copy link

Link copied!

Variables - yes, collections - no. Between my two apps, 1 does not really use either, but has the same issue
RandyHayes 76,299 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@kkawtoski

It's very hard to tell you a specific "this is it" because there are so many factors involved.

I would do a couple of things:

1) Add a Label in the app screen and set the text property to the LookUp of a specific record and column.

Go into your datasource and change that exact record and column and then back in your app, hit the refresh and see if it refreshes or not.

2) Use the monitor tool to see what is going on at the time you hit the refresh button.
kkawtoski 22 on at

Like
a
(0)

Report
Copy link

Link copied!

I've already tried #1, and it took 3 refreshes for it to show the change. I'll mess around with #2
kkawtoski 22 on at

Like
a
(0)

Report
Copy link

Link copied!

Still don't know what the issue is. I created a SP list with 1 item, and a screen with a gallery of only that 1 item. Made a change in SP, and refreshed in the app, had to refresh 2x. Can't get any simpler than that. I tested it back and forth for 5 minutes, every time I had to refresh multiple times. I don't understand why Microsoft would change something in PowerApps so fundamental as the refresh function.