cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
objectivelyLost
Helper I
Helper I

Is it possible to temporarily disable the OnVisible property for a screen?

I ran into an interesting scenario just now.  While debugging, I used a Select() function in to OnVisible property of one of my screens.  I was copy/pasting a lot of items, and accidentally pointed the Select() to a button which has it's OnSelect property set to a Navigate() function pointing to another screen.  Clearly, this is problematic, since I can't get back to the screen now to either delete the button or change the OnVisible formula.  

Luckily, this was only a test screen, so it's not detrimental to the app functionality, but if it happened on another screen, it could have been a lot worse.  It's also annoying that I now have a useless screen that I can't delete.  Is there any workaround to temporarily disable either the button or screen to fix it?  I know I can roll back to a previous version, but I'd rather not if there's an easier way.

1 ACCEPTED SOLUTION

Accepted Solutions
timl
Super User
Super User

@objectivelyLost 

The way I would fix this would be to use the context menu in the tree view to 'duplicate' the screen that your formula navigates to. 

I'd then delete the orginal 'target' screen. If you now attempt to open the screen with the Select formula in the OnVisible property, the call to Navigate will fail because the target screen no longer exists. You can then remove the formula in the OnVisible property.

Finally, you can rename the screen that you duplicated back to the original name. The controls on the duplicated screen will be named differently, but your app should still work. I suspect this approach would be easier than rolling back to a previous version.

 

View solution in original post

3 REPLIES 3
timl
Super User
Super User

@objectivelyLost 

The way I would fix this would be to use the context menu in the tree view to 'duplicate' the screen that your formula navigates to. 

I'd then delete the orginal 'target' screen. If you now attempt to open the screen with the Select formula in the OnVisible property, the call to Navigate will fail because the target screen no longer exists. You can then remove the formula in the OnVisible property.

Finally, you can rename the screen that you duplicated back to the original name. The controls on the duplicated screen will be named differently, but your app should still work. I suspect this approach would be easier than rolling back to a previous version.

 

@timl 
Thanks, That did the trick.  I used a slight variation though in that I deleted all of the controls out of the duplicated screen and then cut/pasted them from the original into the duplicate so that I could retain the original names.  Like it never happened!

timl
Super User
Super User

@objectivelyLost 

That's a great tip about deleting the controls on the duplicated screen, and cutting/pasting them onto the original screen to preserve the original names. Thanks for sharing that!

Helpful resources

Announcements
Power Apps Africa Challenge 2022

Power Apps Africa Challenge

Your chance to join an engaging competition of Power Platform enthusiasts.

Super User 2 - 2022 Congratulations

Welcome Super Users

The Super User program for 2022 - Season 2 has kicked off!

September Events 2022

Check out all of these events

Attend in person or online, there are incredible conferences and events happening all throughout the month of September.

Government Carousel

New forum: GCC, GCCH, DoD - Federal App Makers (FAM)

In response to the unique and evolving requirements of the United States public sector, Microsoft has created Power Apps US Government.

Users online (1,876)