Power Apps Upcoming Features and other Settings
Vložit
- čas přidán 24. 07. 2024
- #powerapps #PowerPlatform #canvasapps
Dive into the often overlooked but crucial aspect of Power Apps: the settings menu. Whether you're a beginner or an advanced user, understanding the settings can significantly impact your app's performance and functionality. This video provides a comprehensive walkthrough of the Power Apps settings, highlighting what to turn on, what to turn off, and the implications of each setting. Learn about app icons, autosave features, app-specific settings, display options, and the importance of keeping up with upcoming, experimental, and retired features. Discover tips on optimizing your app, like using the 'keep recently visited screens in memory' option for faster performance, and understand the trade-offs involved. Stay informed about the latest Power Apps updates and how they can enhance your app development experience.
Up your Power Apps Skills Today!
www.powerapps911.com/up-your-...
0:00 Power Apps Settings
0:40 General Settings
3:43 Display Settings
5:11 Upcoming features
6:35 Preview features review
10:00 Experimental features review
11:27 Retired features review
12:51 Support Settings
Do you need some help on something that you are working on, contact us!
www.powerapps911.com/contact
PowerApps911
www.powerapps911.com/
Let's connect on social!
Twitter: / shanescows
Facebook: / powerapps911
Instagram: / shaneyoung911
LinkedIn: / cincyshane - Věda a technologie
Thank you for this video Shane
Have a great day!
Just to add more on that last point, Shane. I would say NEVER change the app authoring version to newer than the recommended version. You can lose work if that version gets tweaked. Stay with the recommended version. As always, great video!
Great Point Patrick, no reason to play with fire.
Here to report dev tenant is now showing an error that “Navigation is not permitted in App.OnStart”. Toggle is on to allow it in settings. Tuned it off and back on with saves in between, same. Great vid as usual!
SInce for PRD apps, we cannot yet use Git version control, what do you recommend can be done right now. How do developers sync their changes, together, do they work on same solution in same environment but different components etc?
For TextInput Control, the firing of OnChange event seems a bit off. The event is not triggered until you tab/enter out or select another field on the form.
Yes, because the control doesn't Change until you leave it. Might not be the way you want it to work but it is how it has worked for as long as I can remember. 🙂
Does Releasing new changes on PowerApps and analyzing impact on existing apps (Release Management)
A PDF function works well, when it use data from a container. You just run a flow giving container content and everything works fine. Old good HTML to PDF is less reliable as One drive services sometimes crashes.
Yeah, I look forward to the PDF action not being Experimental so we can start to use it. :)
while watching this, i'm wondering about a video about tips and tricks for making stable apps that wont need maintenance every month or two
Hi Shane. Regarding to the feature "Keeps recently visited screens in memory", what happens to the variables or things that might be selected on the first screen and passes the information to a second screen?
Variables like that have their own engine that decides if they need to stay in memory or not. Typically if a variable needs to be used only for one screen you should use a Context variable and only use a global variable when needed. Help that engine out use as few resources as necessary.
So if my undestanding is correct, enabling this feature will keep the global variables from one screen to another but the rest will be deleted or reset?@@ShanesCows
@@benjaminlahsen6721 Lets try this a different way.
If the feature is Off (default behavior) - Then Power Apps manages things for you behind the scenes and if you go from Screen 1 to Screen 2 and nothing on Screen 1 is required to render Screen 2 then Screen 1 is flushed from memory. When you go back to Screen 1 then it has to be processed and loaded again.
If the feature is On - Then when you go from Screen 1 to Screen 2, Screen 1 stays loaded in Memory. So when you navigate back to Screen 1 it shows instantly because it doesn't have to be processed again.
The idea is if Screen 1 takes 10 seconds to load into memory because you have a lot of data sources and calculations switching back is no fun. Turn the feature on and now you don't need to wait those 10 seconds. The downside is you use more memory.
Variables are handled with a different engine and aren't affected by this setting as best I know.
@@ShanesCows now I get it :)!! You the best
I hate the non-blocking onstart. It breaks everything.
Yeah, I get why they do it but I like OnStart the way it used to be best. :)