I am using a loading spinner I found on loading.io. I am using a refresh button and my code on it is this...
My issue is that the update property will make the spinner disappear before the actual refresh goes through. Aside from setting a manual delay of a few seconds on the context variable, is there any way to time that variable closer to the actual refresh speed in order to accurately represent the load?
Yes, this data is being loading via on-premise SQL server so the load can take a bit, but not always. What I am seeing is that sometimes the spinner goes away before the data is actually refreshed on screen. i.e. a user can click forward prior to all data being fully updated
You might check to see what the LoadingSpinner property is set to as there are three choices:
"None" is, of course, to not show the spinner. If you have "LoadingSpinner.Data", you may try "LoadingSpinner.Controls". I switched to it as I was having some of the same issues. My intrepretation was that, while the data was loaded, there were still things like calculations happening which delayed data from appearing. For me, after changing to "Controls" it seemed to not hide the spinner until all items were ready for use. Maybe give that a go?
Nice! I've never tried LoadingSpinner. before. Always wondered what that was for/how it worked.
Can't find any docs on the feature!
I couldn't find any docs either. Hopefully they'll show up soon!
One interesting thing: it uses the background image/color from the page you using it on. This allows for showing the user a full screen picture with the spinner if you have an image there, which can provide a nice transition when items load in.
So...I just realized that I misread the original post @Pseifert . My apologies for the rabbit trail! If you are looking for a screen-to-screen spinner, my comments on the LoadingSpinner are more relevant.
However, my comments about calculations and the like are relevant to the use of context variables as triggers. PowerApps can tell if the data is loaded, which will initiate the context variables, but calculations and such are outside of that scope so the expected behaviors don't always happen (i.e. things may appear sooner than expected). You may look at the what is happening throughout your app and see if there are other items you could use as a trigger condition?
Check out new user group experience and if you are a leader please create your group
Next call is happening on April 21st at 8a PST.
See the latest Power Apps innovations, updates, and demos from the Microsoft Business Applications Launch Event.
ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.