How to Click on a button on a different form

[vsslasd]

How does one Click on a button on a different form?

Select(Button1) works if Button1 is on the current form.

But what if Button1 exists on another form ?

Can this Button Click happen in the background, or must the form appear after it it has been navigated to ?

[RandyHayes]

@vsslasd 

Hmmm...got me wondering now.  I don't see that behavior in any of our apps, so let me do a little experimenting and see if there is something that might impact that action.

[vsslasd]

Thank you.

I've tried turning off all App Settings and the same exact results, so it isn't App Settings.

[RandyHayes]

@vsslasd 

Well blow me down...I am seeing the same issue now too.

Argggg... this is one of those things that worked flawlessly before!!!  

I'm surprised I'm not hearing issues from some of my app users.  I'll have to investigate that, but, yes, this is an issue.

@Anonymous @Mr-Dang-MSFT or to whomever might know or have some input...

Issue in summary is:  Toggle control on another screen responds to changes in default value regardless of the screen the user is on.  This appears to now only work properly in design mode.  The current players are not supporting it.  

[Mr-Dang-MSFT · Accepted solution]

Controls on other screens will not trigger their actions unless the active screen has a dependency on the control from the other screen. The control must be referenced somewhere. This is by design.

Here's the pattern I use:

Screen5

ToggleButton.Default
runPatch

ToggleButton.OnCheck 
Patch(...); Set(runPatch, false)

Screen2

Button.OnSelect:
Set(runPatch, true)

So Screen5 has a dependency on a variable from Screen2. Screen2 just needs a dependency on the toggle. Somewhere on Screen2, make a reference to: ToggleButton.Value. This could be in a label.

[RandyHayes]

@Mr-Dang-MSFT 

YES...the pattern I use as well!

BUT, this no longer works in the players, only in design mode.

[Mr-Dang-MSFT]

@vsslasd, please do not turn off all the settings. I've just tested this and there is no issue. My app has default settings on.

• Everything in the top section but 'explicit column selection' toggled On
• Everything in the bottom section toggled Off

I've attached an app with the same pattern. I've confirmed the pattern works in browser and mobile.

[Mr-Dang-MSFT]

@RandyHayes, can you run my sample and let me know if it is working for you?

[RandyHayes]

@Mr-Dang-MSFT 

Okay...I have identified the issue thanks to your sample app. 

As I looked at it, it was absolutely identical to a test app I threw together.  There was ONE difference...you have a label on your screen to show the value of the toggle.  I had a label as well, but I was showing the value of the global variable instead of the toggle.

If you delete that label on your app, it will no longer work in the player - works fine in design.

Conversely, if I change my label to show the value of the toggle on my other screen, my app works fine in the player.

This is new!  Never had that before....

[Mr-Dang-MSFT]

It normally doesn't affect anyone since they typically have had a dependency on the control somewhere on the screen by chance.

It's really only affected @KroonOfficeSol, you, and myself because we use this pattern 😂

[RandyHayes · Accepted solution]

@Mr-Dang-MSFT 

That is definitely explaining why I'm not hearing cries from any of my app users.  Since I typically will put most all formulas of redundant need or of any substantial complexity on a dedicated screen...and then use a toggle to "call" them, I am pretty sure that most apps have some dependencies.

But, I can see getting into trouble with this - only because trouble lurks when you can do one thing in design and it doesn't work in play. 

As for @vsslasd , I suppose in this case, if a dependent control is placed on the "calling" screen (even if not visible), that would solve the issue.