, Navigate action in Power Apps App.OnStart is now deprecated

Navigate action in Power Apps App.OnStart is now deprecated

Navigate action in Power Apps App.OnStart is now deprecated


or a large amount of Ability Applications, I use a conditional Navigate() action in just my Application.OnStart to figure out which display screen the person should be redirected to when loading the app. But as of now, it is no lengthier supported to use a Navigate motion inside of the OnStart of your Electricity Application.

In this short weblog, I will explain to you how to make confident you can nonetheless direct people to an additional display when loading your application.

To start with of all, don’t get worried that your Electric power Applications will not do the job any more as of now. This alter only demonstrates the newest framework variation of Electric power Apps.

I’m not guaranteed which version accurately, but it appears like setting up from variation 3.211xx.xx, Navigate is no for a longer period supported inside of the Application.OnStart. You can check the existing framework model of your Ability Applications in the edition historical past of your app:

Variation in which Navigate is supported in just Application.OnStart

Variation in which Navigate is not supported inside Application.OnStart

, Navigate action in Power Apps App.OnStart is now deprecated

So your previous apps will proceed to get the job done, but it does necessarily mean that when you start off earning alterations from now on, you will mechanically be on the newer framework version and that it is no more time supported.

There are two means to make sure your customers will still be redirected to one more display when loading the Energy Application:

  1. Re-enable Navigate within just Application.OnStart (briefly)
  2. Use App.StartScreen as a substitute of App.OnStart

I will reveal the two approaches beneath.

Re-enable Navigate inside App.OnStart

This is the fastest system, but also a momentary just one since Microsoft in the long run desires you to use the system as explained down below. It in essence comes down to re-enabling the Navigate() motion in just your OnStart. For present applications, this characteristic will mechanically be enabled.

For new applications, you can help this by heading to File > Settings > Future functions > Retired and permit the ‘Allow the Navigate purpose in Application.Onstart‘ feature:

, Navigate action in Power Apps App.OnStart is now deprecated

This will allow you to retain applying the Navigate() motion in your OnStart for the time currently being. But sooner or later, this attribute will be retired and you want to use the strategy as described under.

You will also be prompted with a warning that it is not encouraged to use the OnStart for this conduct:

, Navigate action in Power Apps App.OnStart is now deprecated

Use App.StartScreen as a substitute of OnStart

To make certain your applications will continue to keep doing work for a longer period of time, you have to have to configure your App.StartScreen to set the start out display screen of your app.

, Navigate action in Power Apps App.OnStart is now deprecated

This can be carried out in a static way or dynamically employing a issue:

, Navigate action in Power Apps App.OnStart is now deprecated

This also implies you don’t will need to have the start display screen as the very first display screen in your tree watch. You can just set the display of your preference as start screen, no matter if that is the initial, second or even the very last display in your tree look at.

You should make positive to pick out either a static or dynamic formula, usually it will not operate.



Supply website link