Navigate(HomeScreen,ScreenTransition.UnCover)ĭon’t worry about every line, look for the Set(RefreshAcitivty lines, that’s the good stuff. Set(RefreshActivity, "Refreshing Activity.") ClearCollect(Pledge,Filter('.',UserID = CurrentUser.ID)) Set(RefreshActivity, "Refreshing Pledge.") Set(RefreshActivity, "Refreshing Questions.") Set(CurrentUser,First(Filter('.',Email = User().Email))) Then, on the button’s OnSelect property, I have this block of code: There is a label right below the button and the Text property is set to RefreshActivity. Set(RefreshActivity,"You will be sent back to the home screen when complete.")
#Data toolbar not loading how to
How to get it doneįirst, using OnVisible of the screen, I set the message variable as follows, so they have some heads up as to what’s going to happen. In this example, as you can see, the user sees more going on, feels better that nothing might be stuck. Here I give the user a status as it makes it connections and refreshes each data source. On the Reload screen, there’s a button, and they press that to refresh all of the data connections. In this same app, the user can optionally reload the app’s data, which is basically like reopening the app. You could replace my text label with an animated gif and have something a little more visually stunning. Those will only appear when AppLoaded is true.Įasy enough right? Very simple. Then the two buttons that appear, “Log Today” and “View My Activity”, Visible properties are set to AppLoaded.When AppLoaded is false, it will display this object. The label stating “Give us just a moment…” Visible property is set to !AppLoaded.From here, we want to set the visibility of our controls based on this variable AppLoaded. This is located at the end, after all of the database calls and business logic that needed to run completes. Then at the bottom of the same OnVisible property, I set it to true:
#Data toolbar not loading code
In this app I’m using the OnVisible property of the Home Screen, in which my first lines of code are: Instead of just letting PowerApps take it sweet time, I present the user with a basic screen asking them to wait:Īt least the user knows something is going on. In my app (in this example, my app is for users to pledge to be more environmentally aware of their day to day), on the initial home screen load, I query Azure SQL to get the user’s information, their questions and pledge information. Don’t you like to know what an app is doing, even if it takes 2 seconds to do it? Create a loading message in PowerApps We want to tell the user that something is happening, as fast as we can, so they can wait, and maybe even be okay with waiting as long as they know. Your users can’t leave the app since it’s required for their job, but why frustrate them? We have to do what we can to improve their experience, to not add to their stress. I’ve come to find that waiting on data to load in PowerApps can sometimes live in the 1000ms to 10000ms window, 1 second to 10 seconds! During this time, your users are losing focus, and want to leave. I find it really fascinating and accurate, think about your own interactions with apps, if you can think “what is taking this so lo…” then it loads, you’ve waited too long.
![data toolbar not loading data toolbar not loading](https://barryvdh.nl/img/posts/debugbar-telescopetoolbar/ajax_toolbar.png)
The above is Google’s point of view of user’s perception of waiting in an app. For most users on the web, loading pages or changing views represents a task.īeyond 1000 milliseconds (1 second), users lose focus on the task they are performing.īeyond 10000 milliseconds (10 seconds), users are frustrated and are likely to abandon tasks. Within this window, things feel part of a natural and continuous progression of tasks. Users experience a slight perceptible delay. Any longer, and the connection between action and reaction is broken. Respond to user actions within this time window and users feel like the result is immediate. That’s 16ms per frame, including the time it takes for the browser to paint the new frame to the screen, leaving an app about 10ms to produce a frame. They perceive animations as smooth so long as 60 new frames are rendered every second. Users are exceptionally good at tracking motion, and they dislike it when animations aren’t smooth. Your user’s perception is what defines your success, it’s what drives designers and app developers a like to make sleek, intuitive, and just plain cool apps. Pay attention at the wee top of your app, you’ll see some dots flying around PowerApps does have that useless little loading dots thing at the top, which most people don’t see: There is nothing that drives users more nuts than just staring at a screen as it does nothing, wondering if it’s frozen or broken. Depending on where your data lives, it may take a few seconds for that data to display in the PowerApp.