How to Migrate from App OnStart - Power Apps 2022
HTML-код
- Опубликовано: 6 мар 2022
- Changes are coming to Power Apps, here’s what you should do to start moving away from App.OnStart
Full Blog Writeup: www.bulb.digital/blog/migrati...
💡 Check out the Internal Communication Guidebook we mentioned: www.viaworkplace.com/
If you found this video helpful, subscribe to always be in the know of O365. This whole channel is focused on creating content around the Microsoft space. We create videos on Sharepoint, Power Platforms, Planner, Outlook, and other M365 tools. Technology should be an enabler, not a barrier, to productivity and happiness at work. Our mission is to empower your workforce through technology.
Check out a more in-depth blog in this topic here! www.bulb.digital/blog
Other Free Resources + Guides 👇
📧 Subscribe to our weekly newsletter. Tips and tricks sent straight to your inbox every Thursday! www.bulb.digital/newsletter
✅ Take our free Office Assessment to see how your workplace stacks up! officeassessmentscorecard.sco...
💻 Join Office Hours! Ask your O365 questions live with us every first Wednesday of the month. www.bulb.digital/office-hours
🔗 Looking for a supportive community for shared insights and collective growth?www.viaworkplace.com/the-work...
💡 Need large scale Office 365 help? www.bulb.digital/services
Presenter: Mike Bodell 
Наука
Great tutorial. Thanks for the workaround!
Thanks Jim! Glad we could help.
Really like all your tutorial videos. Newbie here in Power Apps, hope to see more videos from this channel. 😊
Thanks! We'll keep them coming :) You may find our Intro to Power Apps Course helpful if you're looking to learn more! www.bulb.digital/courses/intro-to-power-apps
great stuff - thanks
No problem, glad we could help!
Very helpful👍
Glad to hear that Zaid!
Thanks. But how could I navigate to different screens without touching param variable? Seems like it need to use param function to change the URL and redirect screen.
That's the point about the deep link scenario. We're inspecting the ID parameter to make the decision. Alternatively, you could use something else, like a property from the user's profile to make a similar navigation decision.
Additionally, don't forget that we also linked between the gallery screen and the form screen via the Add icon (button) in the upper right of the gallery screen or by selecting / clicking an item in the gallery. In both of these cases we added a Navigate function to the OnSelect property.
Thank you! One thing I'm still not clear is why the need to remove OnStart. If for initial loading performance of the app, then it's just forcing users to come up with workarounds that still have the same or even longer wait time, isn't it?
Moving away from using the App.OnStart is required in the scenario you were using the Navigate function in the OnStart property. It simply won't work anymore. Secondary to this, the migration away from using this property to initialize our applications is intended to prevent long-running complex formulas from slowing the start up time. This specifically blocks the "first screen" of the application to load and leaves the user staring at Microsoft's PowerApps loading spinner.
It could be said that maybe Microsoft didn't like us putting long running complex code in the OnStart because it's Microsoft's screen that everybody stares at while our apps take so long to load and that may cause misdirected blame for a "slow" app. So now, you have to give them a screen to look at while your data loads.
The other thing to be aware of is that Microsoft is working on a couple other things to make this better. This includes something called "named formulas" along with prefetched and cached data. These mechanisms will allow us to eliminate much of the data loading we do today, by either setting global variables or collecting datasets.
@@BulbDigital 1. Do you understand they can just block the Navigate function in the OnStart property right?
2. And about the attempt to prevent long-running complex formulas from slowing the start up time, now it will leave the user staring at a Developer's loading spinner. 🤔
@@abdielruiz1332 We're looking forward to seeing what Microsoft ends up doing with the next iteration of this stuff. We're caught in a little bit of a limbo transition period unfortunately. One cool thing we've been checking out is the "Named Formulas" feature that's in development and helps with app initialization.
Thank you for this great workaround, but we're now january 2023 and the OnStart is still available in Power Apps. Has Microsoft changed it's view on this item, or has it just delayed the deprecation ?
As far as we know it's still deprecated, just not removed from the platform in order to support existing apps. By default for new apps, last we checked, OnStart is disabled and has to be toggled on (though still deprecated) in order to use it.
@@BulbDigital is there a MS KB article about this?
Incredible tutorial! Just one question... How can we get to that loading screen once the app is open?
Cool you reacted! Were you able to find out how can we get to that loading screen once the app is open? Thank you so much!
You can point the App.StartScreen property at your loading screen to use it as your first screen. The loading screen isn't a template within Power Apps, it's just one we created. Skip to 5:41 to see where this is configured.
If that doesn't answer your question, let us know where we're missing information to help you out.
@@BulbDigitalThanks for your answer! The thing is that, with the app open, when clicking on a push notification from the app the loading screen nor the StartScreen is loaded... It just keeps in the same screen and parameters aren't renewed. Do you know how can I address that? Thank you😊