cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Error: Incompatible types for comparison. These types can't be compared: Error, Text

Hello All,

 

Hope someone has had this happen to them before and knows just what to do, I'll try to keep it short and describe things as simply as possible.

 

I keep getting the error mentioned in the Subject:  Incompatible types for comparison. These types can't be compared: Error, Text.

 

I have two fixes for it so that I can continue working on the app, when I log out and log back in, I have to apply 'the other fix'.

Here are the two fixes:

  1. If(var_selVer<>"",UpdateContext({s5_SelVer: var_selVer}),UpdateContext({s5_SelVer: Blank()}));
  2. If(!IsBlank(var_selVer),UpdateContext({s5_SelVer: var_selVer}),UpdateContext({s5_SelVer: Blank()}));

So, currently the app is working, items 1 & 2 above are in the OnVisible property of the screen.  I log out, then log back in and Item 1 gives the error.  The fix is that I rem Item 1 with a // and un-rem Item 2 and the app works just fine.  Then after I log out, when I log back in Item 2 gives the same exact error, so I rem Item 2 with a // and un-rem item 1 and the app works just fine!

 

WHY is this happening!?

 

A little background on the behavior.  While there are multiple screens in the app, I'll just limit it to 3 screens to describe the desired behavior:

  1. Home Screen
    1. clicking a Button will Navigate to Middle Screen
  2. Middle Screen
    1. clicking a Back icon takes the User back Home,
    2. clicking a View Button, Navigates the User to the Last Screen and sets the variable by using Set(var_selVer, s5_SelVer)
  3. Last Screen
    1. var_selVer is used to filter the galleries on the screen so the User can view a bunch of summaries of the previous screen's data
    2. clicking a Back button Navigates the User back to the Middle screen and Item 1 or 2 Works to return the user back to the version they were working on when they left the screen.

The desired behavior is that the selected version is cleared when the user navigates from First Screen to Middle Screen and that the selected version is kept when the user navigates from the Last Screen back to the Middle Screen.

 

s5_SelVer is populated in one of two ways.

The first way is when the User creates a new Version.  When an Add icon is clicked in a Form the entry is Patched to a SQL Table and at the same time the entry is set in the variable by using Set(s5_SelVer, EnteredVersion.Text)

 

The second way is when the User enters the screen, if a Version already exists, then the User can click one of the Versions in the Gallery and select it.  When this happens UpdateContext:({s5_SelVer: ThisItem.Ver}) sets the variable.

 

I know there has to be a simpler way, but I keep getting tied up in the logic of it I guess.

 

Short version of desired behavior, when Navigating from Home no version selected when the middle screen loads.  When Navigating from Last Screen back to the middle screen, remember the what the version was when you left and apply it when the middle screen loads.

 

Any help would be greated appreciated!

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

@More2Learn ,

Looking at it again, the issue may be that s5_SelVer is being called on Middle Screen before it is initiated (and your fix does this). I generally initiate any Context Variables at Screen OnVisible to ensure any code referring to them is valid, so

UpdateContext({s5_SelVer: Blank()})

at that point would do that. Also, your Global Variable can be set at App OnStart and this would not cause any issues doing.
Another thought (and may not be the "textbook" answer), but if you are passing Variables around between screens, consider making them Global.

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

MVP (Business Applications)   Visit my blog Practical Power Apps

View solution in original post

5 REPLIES 5
WarrenBelz
Most Valuable Professional
Most Valuable Professional

Hi @More2Learn ,

What other places to you use var_selVer and s5_SelVer and what type of value do you set it to ? The issue may be that you may be using it as a number somewhere as "" (empty string) sets it as Text and from that point it becomes a Text Variable.  

Mr. Belz,

 

Thanks for your quick reply.

 

As far as I know within the app, the only value I ever pass to that variable is alphanumeric.  It is possible that the user 'could' enter a numeric only version, but that is pretty unlikely since I'm having them include their initials in the version number.  I'm also validating the data before it's patched to SQL so they can't enter any symbols and such.  Right now, I am the only one in the tables, developing the app, and I don't have any numeric only values for that field.

 

At present the only place that s5_selVer is used is on the Middle Screen and var_selVer is set in the Middle screen and passed to the Last Screen and the Last Screen is the only place that var_selVer is used.  When the user clicks the View button, s5_selVer is passed to var_selVer, i.e. Set(var_selVer, s5_selVer).  As a test I even put UpdateContect({s5_selVer: Blank()}) right after I set it to var_selVer, like this:  

 

Set(var_selVer, s5_SelVer); UpdateContext({s5_SelVer: Blank()}); Navigate(scr_Last, ScreenTransition.Fade)

 

Is there anything else I can check for you on this?  Thank you for your interest!

@More2Learn ,

Looking at it again, the issue may be that s5_SelVer is being called on Middle Screen before it is initiated (and your fix does this). I generally initiate any Context Variables at Screen OnVisible to ensure any code referring to them is valid, so

UpdateContext({s5_SelVer: Blank()})

at that point would do that. Also, your Global Variable can be set at App OnStart and this would not cause any issues doing.
Another thought (and may not be the "textbook" answer), but if you are passing Variables around between screens, consider making them Global.

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

MVP (Business Applications)   Visit my blog Practical Power Apps

Mr. Belz,

 

Apologies for not getting back to you on this sooner!  I just got around to being able to chase it down myself.

 

Sometimes it helps to just be away from a problem for a bit to help you see the solution (your answer & applying it took me about 5 minutes!  THANKS!).

 

I think your response was spot on.  Primarily due to a lack of full understanding on my part.  I will sum up what I believe the problem was and the fix I implemented based on what I believe your advice to me to do.  If I have gummed it up, please correct me so that this might help someone else in the future.

 

Without restating all of the text in the original post.... I have 3 screens (Home, Middle, Last).

When Home navigates to Middle - open up without a selection

When Middle navigates to Last - push the selection to last with a Global Variable (var_selVer)

When Last navigates back to middle - remember the selection and apply it.

 

My problem was that I was trying to make my variable (s5_selVer) be both Global (Set) and Local (UpdateContext).  Because I just want s5_selVer to be used on that screen only, it should just be Local.  The conditions that I was placing on it were both Set & UpdateContext in different places/screens, both can't always be true, so sometimes (when I was running the app) it would work because I'd already established the setting of it.  But when I closed and reopened it, the Sets & UpdateContexts weren't agreeing with each other causing problems.

 

So the fix:

On my Home Screen OnVisible Property I did:  Set(var_selVer, Blank())

this same thing could also be done at the App OnStart Property instead, but I want it to happen everytime a User goes to the Home screen, not just when the app starts.

 

On my Middle Screen On Visible Property I did: 

If(!IsBlank(var_selVer),UpdateContext({s5_SelVer: var_selVer}) && Set(var_selVer,Blank()),UpdateContext({s5_SelVer: Blank()}))

 

On my Middle Screen button to navigate from Middle to Last: 

OnSelect Property:  Set(var_selVer, s5_SelVer);
UpdateContext({s5_SelVer: Blank()})

 

Thanks again for your help and insight, very much appreciated!

Hi @More2Learn ,

As long as you understand that s5_SelVer is three different variables with three different concurrent values depending on the screen you are on. We all work different ways, but for the sake of my sanity, I never name two Context Variables on different screens the same and if passing values between screens, I use a Global Variable.

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