Answered

Navigate Context Variable

(0) Share

Report

Posted on by tdupton

It seems I can't pass a variable via navigate any longer. No matter what the variable is, I get the same error: "Context variables cannot be used here. Context variable can only be bound to a single, specific screen". Anyone else see this?".

Categories:

Building Power Apps

I have the same question (0)

All responses (10)

Answers (1)

Shanescows 2,218 Most Valuable Professional on at

Like (1)

Report

Maybe we need more details? Where are you putting this property and on what type of control?

I just created a button and for OnSelect I did Navigate(Screen2,ScreenTransition.Cover,{BestPowerAppsConsultingCompany: "PowerApps911"}) and it works.

Was this reply helpful? Yes No
tdupton 57 on at

Like (0)

Report

I’ve tried OnSelect on a gallery and OnChange of a dropdown. Both give me the same error. I’ve tried the web client and Windows client with same results. I’ve done this dozens of times before so I don’t know if it’s some sort of a new bug or if I’m just having a senior moment.

Was this reply helpful? Yes No
Shanescows 2,218 Most Valuable Professional on at

Like (0)

Report

ThisItem.Screen is what is confusing me. Try hardcoding Screen1 (or whatever your screen name is) and see if that works.

Was this reply helpful? Yes No
tdupton 57 on at

Like (0)

Report

The gallery is filled with a collection. That is where the thisitem.screen comes from. Here is the collection:

ClearCollect(PanTypes,
{Name: "Salary Change", Screen: PANSalaryChangeScreen},
{Name: "Transfer", Screen: TransferPanScreen})

Was this reply helpful? Yes No
tdupton 57 on at

Like (0)

Report

But, you know what, that was it. I hardcoded a screen and it worked fine...I know I've set up a collection like this before and it worked fine. Is there a syntax issue?

Was this reply helpful? Yes No
Verified answer

Shanescows 2,218 Most Valuable Professional on at

Like (1)

Report

I have never gotten a function to accept data like that or via a variable. It annoys me a lot. 🙂

What you would have to do is make your Onselect an If.

If( ThisItem.Name = "Salary Change", Navigate(PANSalaryChangeScreen,Cover),
ThisItem.Name = "Transfer", Navigate(TransferPanScreen,Cover)
)

Something like that should work.

Was this reply helpful? Yes No
tdupton 57 on at

Like (2)

Report

Thanks for the quick response, Shane. That's a pain in the butt!

I hope they offer something like that for us soon.

Was this reply helpful? Yes No
Slaverty 218 on at

Like (0)

Report
Or a switch for little easier on the eye.

Switch( ThisItem.Random,
"Screen1",Navigate(Screen1, Fade),
"Screen2",Navigate(Screen2, Fade),
"Screen3",Navigate(Screen3, Fade),
"Screen4",Navigate(Screen4, Fade)
)
Really annoying we can't just put the variable straight into the Navigate though. Another use case, I have a Middle-Man screen hop where control property variables (colour, size ect) are defined on splash. Some of these are taken from a "User Settings" table. When user changes settings, it hops back to splash to re-do all the property variables then hops back to the screen the user was last on.

I had hoped I could just define a global variable containing the current screen's name on the OnClick of the Settings button (eg Set(gloSettingsReturn, Parent.Name)), then simply have Navigate(gloSettingsReturn) on my splash page, but nooo. Now I need a big fat Switch.

Was this reply helpful? Yes No
NicolasK Microsoft Employee on at

Like (0)

Report

What is strange is that it was working previously. I've got an app that I built about 2 years ago. Some formula involved variables to define the navigate screen and it was working perfectly fine. I updated the app today, and now I have this error 😞

Was this reply helpful? Yes No
rschneider 75 on at

Like (0)

Report

I've created an Idea for this:
https://powerusers.microsoft.com/t5/Power-Apps-Ideas/Let-Navigate-also-use-variables/idi-p/732599#M32207

Was this reply helpful? Yes No