cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Steets
New Member

PowerApps does not correctly handle Navigate() context records on screens navigated to by variable name.

Hello! I'm currently writing an application and have encountered an inconsistency in how PowerApps handles local variables when passed using the Navigate() command. When navigating to a screen whose name is specified using a context variable from the previous screen, the records are not created properly. It's a bit difficult to explain, so let me use an example:

 

Example:

An app has three screens, "One", "Two", and "Three". On each screen, there is a button containing the below-listed OnSelect code.

 

Screen One: Navigate(Two, None, {forward: Three, back: One})

Navigate to screen two using no transition, passing the records "forward" and "back".

Result on button press: PowerApps navigates correctly to screen Two. Variables "forward" and "back" are set up properly.

Screen Two: Navigate(forward, None, {forward: Blank(), back: back})

Navigate to the screen specified in the variable "forward" (Three) using no transition, passing the records "forward" and "back".

Result on button press: PowerApps navigates correctly to screen Three. Variables "forward" and "back" are NOT set up properly on the next screen and cannot be read.

 

Screen Three: Navigate(back, None)
Navigate to the previous screen using no transition.

Result on button press: PowerApps fails to navigate, as the "back" variable was not set up properly on the previous screen.

 

Further experimentation leads me to believe this problem is exclusive to Navigate() calls where the page destination is a variable name specified in a context record; navigating to pages defined with an on-page UpdateContext() call function as intended.

 

If you're wondering what my use case for this weird page navigation structure is, I have a screen whose functionality is very simple: given a list of objects, ask the user which object in that list they'd like, then proceed to another page, passing the single item along. On the final page, there is a back button that skips the list-selector page by carrying the origin page's name in continually-passed context records.

 

Any help or potential workarounds would be appreciated. Thanks!

1 ACCEPTED SOLUTION

Accepted Solutions
iAm_ManCat
Most Valuable Professional
Most Valuable Professional

This is because you are trying to set a context variable to a different type - it doesn't show it explicitly because of the way you are passing them between screens. When you try set it to Blank(), you would normally get an incompatible type error as Screens and Blank() aren't the same type. The type mismatch then breaks your navigate as it can't navigate to 'error'.

 

As a workaround, I would set and update a global variable instead of passing a context variable repeatedly. I don't think context variables are meant to be passed on repeatedly in this way, that's kinda the point of global variables.

 

Screen1 Forward button

Set(ForwardScreen, Two); Set(BackScreen, One);
Navigate(ForwardScreen, ScreenTransition.None)

Screen1 Back button

Set(ForwardScreen, Two); Set(BackScreen, One);
Navigate(BackScreen, ScreenTransition.None)

 Screen2 Forward Button

Set(ForwardScreen, Three); Set(BackScreen, One);
Navigate(ForwardScreen, ScreenTransition.None)

Screen2 Back button

Set(ForwardScreen, Three); Set(BackScreen, One);
Navigate(BackScreen, ScreenTransition.None)

 

Screen3 Forward button

Set(ForwardScreen, Three); Set(BackScreen, Two);
Navigate(ForwardScreen, ScreenTransition.None)

Screen3 Back Button

Set(ForwardScreen, Three); Set(BackScreen, Two);
Navigate(BackScreen, ScreenTransition.None)

 

 

ScreenNav.gif

 

I have tested this and it navigates between then without issue.

(attached proof of concept app for you to open and test)

 

Cheers,

Sancho


@iAm_ManCat
My blog


Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you!


Thanks!
You and everyone else in the community make it the awesome and welcoming place it is, keep your questions coming and make sure to 'like' anything that makes you 'Appy
Sancho Harker, MVP


View solution in original post

4 REPLIES 4
iAm_ManCat
Most Valuable Professional
Most Valuable Professional

This is because you are trying to set a context variable to a different type - it doesn't show it explicitly because of the way you are passing them between screens. When you try set it to Blank(), you would normally get an incompatible type error as Screens and Blank() aren't the same type. The type mismatch then breaks your navigate as it can't navigate to 'error'.

 

As a workaround, I would set and update a global variable instead of passing a context variable repeatedly. I don't think context variables are meant to be passed on repeatedly in this way, that's kinda the point of global variables.

 

Screen1 Forward button

Set(ForwardScreen, Two); Set(BackScreen, One);
Navigate(ForwardScreen, ScreenTransition.None)

Screen1 Back button

Set(ForwardScreen, Two); Set(BackScreen, One);
Navigate(BackScreen, ScreenTransition.None)

 Screen2 Forward Button

Set(ForwardScreen, Three); Set(BackScreen, One);
Navigate(ForwardScreen, ScreenTransition.None)

Screen2 Back button

Set(ForwardScreen, Three); Set(BackScreen, One);
Navigate(BackScreen, ScreenTransition.None)

 

Screen3 Forward button

Set(ForwardScreen, Three); Set(BackScreen, Two);
Navigate(ForwardScreen, ScreenTransition.None)

Screen3 Back Button

Set(ForwardScreen, Three); Set(BackScreen, Two);
Navigate(BackScreen, ScreenTransition.None)

 

 

ScreenNav.gif

 

I have tested this and it navigates between then without issue.

(attached proof of concept app for you to open and test)

 

Cheers,

Sancho


@iAm_ManCat
My blog


Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you!


Thanks!
You and everyone else in the community make it the awesome and welcoming place it is, keep your questions coming and make sure to 'like' anything that makes you 'Appy
Sancho Harker, MVP


Hello Sancho, I have been trying to replicate your solution for one of my projects, but I keep getting this error, any idea what I might have been doing wrong here?

 

Neha94_0-1679655322358.png

I need a dynamic value for the screen name and that should come from the QR I am scanning.

 

Thank you in advance!

Neha94
New Member

This is the snap of what I tried 

Neha94_0-1679659912246.png

 

iAm_ManCat
Most Valuable Professional
Most Valuable Professional

Ok, yeah so that's not going to work as we can't navigate to a text value, the Navigate function takes a Screen object as an input, so you'd have to have a condition in the navigate if you're using scan.

 

Also, how are you getting the name of the screen from the scan? This will likely be a number you are scanning, so you'd need to do something like this:

Set(Scan, BarcodeScanner1.Value)

If(Scan = "74819269182", Navigate(Screen2),
   Scan = "68161861181", Navigate(Screen3)
   //etc etc etc
   // you will need to change those values to whatever your barcodes represent
)

@iAm_ManCat
My blog


Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you!


Thanks!
You and everyone else in the community make it the awesome and welcoming place it is, keep your questions coming and make sure to 'like' anything that makes you 'Appy
Sancho Harker, MVP


Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages