cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
GringoInMiami
Advocate II
Advocate II

Changing Home Screen Causes Issue with On Start Actions

When replacing the original Home Screen with another screen, where the original contains On Start actions, the app continues to reference the original Home Screen for the App.OnStart function. In fact, if the original Home Screen is deleted and the new Home Screen contains the same On Start actions, they are not executed and any variables or collections are blank/empty.

 

This is definitely a bug.

 

2018-09-14_11-10-14.png2018-09-14_11-29-57.png

 

 

4 REPLIES 4
v-micsh-msft
Community Support
Community Support

Hi @GringoInMiami,

 

Thanks for the feedback.

It seems the OnStart property will not work consistently with the screen action, like duplicate, delete or move up/down.

 

Please consider switch to Onvisible property as a temporary workaround.

 

I will send the feedback regarding the OnStart property from my side, and update here if I have got any response back.

 

Regards,

Michael

Community Support Team _ Michael Shao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Anonymous
Not applicable

Have seen this as well.

 

The most common "work around" to things like this is to Save the app in studio, exit, and reload.

 

Unfortunately I find myself doing this several times a day to work around some of the quirks like this (and there are a number of them) where things that did work suddenly don't.  But a reload of studio often seems to resolve many of them.

Hi @GringoInMiami,

 

Thanks @Anonymous for the reminder. The symptom should be fixed after a reload. So it is recommended to take re-check the configured formula after a reload.

 

 

The OnStart property has the following explanation documented:

Quoted:

"

OnStart – The behavior of the app when the user opens the app.

  • The formula to which this property is set runs before the first screen of the app appears. Call the Navigate function to change which screen appears first when the app starts.
  • You can't set context variables with the UpdateContext function because no screen has appeared yet. However, you can pass context variables in the Navigate function and create and fill a collection by using the Collect function.
  • When you update an app, the formula to which this property is set runs when the app is loaded into PowerApps Studio. To see the impact of changing this property, you'll need to save, close, and reload your app.
  • The OnStart property is actually a property of the app, not the screen. For editing convenience, you view and modify it as a property on the first screen of your app. If you remove the first screen or reorder screens, this property may become hard to find. In this case, save, close, and reload your app, and the property will reappear as a property of the first screen.

"

Regards,

Mcihael

Community Support Team _ Michael Shao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

I've already tried all the suggestions but the issue remains. The ONLY solution I've found so far is to rename the variables and collections.

Helpful resources

Announcements
PA_User Group Leader_768x460.jpg

Manage your user group events

Check out the News & Announcements to learn more.

Power Query PA Forum 768x460.png

Check it out!

Did you know that you can visit the Power Query Forum in Power BI and now Power Apps

Carousel 2021 Release Wave 2 Plan 768x460.jpg

2021 Release Wave 2 Plan

Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.

PowerPlatform 768x460.png

Microsoft Learn

Check out our new Discover Your Career Path blog post series and get all the details.

Users online (1,111)