cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
TedBabcock
Advocate II
Advocate II

Another "Incompatible types for comparison" error

I'm hoping @RandyHayes has another solution up his sleeve. I am getting the same "Incompatible types for comparison" error that two others have recently reported, but my situation is not like theirs. I have a popup component, cmpPopupOK_AAP that has an input property and an output property, both Boolean. They both default to false: the output property's default is false in the component, and the input property's value is the global variable boolApprPopupVisible, which is set to false in App.OnStart. The visibility of the popup component is when these two properties do not equal each other, which should evaluate to false on startup, thus making the popup not visible. But when the app starts, the popup is visible.

 

I inserted a label to show the value of input <> output, and it shows true when the app starts, even though both values are false. The "<>" sign in the label formula area has blue lines beneath it, and the error message that shows when I hover over it says, "Incompatible types for comparison. The left value is Text and the right value is a Boolean." But the left value is clearly Boolean, and Power Apps even says so:

 

TedBabcock_0-1623694155237.png

 

The right value is also Boolean, as Power Apps says:

 

TedBabcock_1-1623694283657.png

 

But the comparison can't be completed because of the incompatible types error.

 

It doesn't seem to be a problem with App.OnStart. After I render the popup not visible, I click the ellipses by App in the navigation menu and click Run OnStart, but it doesn't suddenly become visible. It's only when the app is opened for the first time that this happens. It doesn't matter if it's opened in edit mode, or just played the way an end user would.

 

Also, it doesn't matter how many times I toggle the value of boolApprPopupVisible, which controls the input property; the popup stays visible. It's only when I change the output property by clicking the component's OK button that the comparison is recognized and the popup disappears. I double-checked both properties in the component, and they are indeed defined as Boolean.

 

I was half hoping that, while going through the explanation and verifying all the steps, I would stumble onto the cause of the problem, but that did not happen. Thanks for any assistance you can offer!

1 ACCEPTED SOLUTION

Accepted Solutions
RandyHayes
Super User
Super User

@TedBabcock 

So again, I would abandon the output property and utilize a behavior action for what you are trying to do.

Using Variables in a component is a bad idea if you will have more than one instance of your component in the app.

At this point there is a bug in components that has gone on for too long, which is that the components share variables across instances - this includes controls in the component.  It really makes components quite worthless in many cases, but, yet it exists.

I make a lot of pop up components like you are doing and the output has never been a good one.  Turn them into behaviors and I believe you will resolve your issues.

 

Seems like you are trying to set the visibility of the component based on once they hit ok button.

If so, I'd suggest the following:

  In your app - when you want the pop up to show, set a variable to something like UpdateContext({lclShowPopup: true})

  Set the Visible property of your Popup component to : lclShowPopup

 

  Create a Behavior property in your Component called : OnOk  (set to Boolean)

  In the button or other action of the component, use set the formula to: Parent.OnOk()

 

In your app component, set the OnOk action that you now have to : UpdateContext({lclShowPopup: false})

 

You can get more mileage out of the pop up with setting the variable to a text value - the text you want to display in your popup to: UpdateContexct({lclShowPopup: "blah blah blah, press ok"})

Then, the visible property of the component to : !IsBlank(lclShowPopup)

The input property of your component for the text of your message to : lclShowPopup

And change the OnOk action to : UpdateContext({lclShowPopup: Blank()})

 

 

 

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

View solution in original post

8 REPLIES 8
RandyHayes
Super User
Super User

@TedBabcock 

You cannot compare input properties of a component.  They are properties to be set, not read.  So in your case you need to compare the property value from the input to the output.

You state that the input property is set to boolApprPopupVisible, so that is what you need to compare the output to.  

boolApprPopupVisible <> cmpPopup_OK_APP.PopupOKVisible_output

 

However, if I had to make a guess, I would say you are trying to determine if a user has selected OK (or something like that) in the component to determine if the component is visible. 

If so, I would highly recommend using a behavior rather than an Output property for this.

 

I hope this is helpful for you.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!
TedBabcock
Advocate II
Advocate II

That's odd, because after I click on the popup's OK button, it works as planned, with the comparison of input and output properties. It's only on startup that it doesn't want to work right.

 

I did try your suggested comparison, and I get the same error message.

 

I'll keep poking around and look into behaviors. I'll post again here if I discover anything. Thanks for your help!

RandyHayes
Super User
Super User

@TedBabcock 

How is your Output property defined in the component?

 

EDIT: oh and sorry, I misspoke on the reading of the input properties.  Yes, you can read those values.  Sorry about that.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!
TedBabcock
Advocate II
Advocate II

@RandyHayes It is defined by a Boolean variable, which is toggled when the OK button is clicked.

 

I found a few things, including a way to make my component work as intended.

 

But first, I found out that the "Incompatible types for comparison" error did not appear when I put the comparison in a label without the concatenated text. Then I tried putting parentheses around the comparison in the concatenated label, and that also made the error message disappear.

 

I set up an OnReset action in the component that does the same thing that the OK button does: toggle the component's visibility variable, which controls the output property.

 

I still had the problem that the component was not evaluating the output value correctly -- it showed it as false to begin with, which should have made the component not visible at startup. It was only when I clicked the OK button twice that the component would go away: the first click changed the output value to true, and now the comparison evaluated correctly, keeping the component visible. When I clicked it a second time, it set the output value to false again, and now the comparison evaluated to false, and the component became not visible.

 

So in my App.OnStart, I included the statement Reset(component) twice, to duplicate clicking the OK button twice. Lo and behold! The component was not visible the next time I opened the app. I triggered it by changing the variable that controls the input property, and the component was visible; and clicking the OK button made it disappear again. So now it's doing what I need it to. The comparison between the input and output values does seem to work.

 

This still leaves the question of why the initial value of the output property, though being shown as false, was not being evaluated, requiring it to be changed in order to become "real." It would be nice to get that problem solved with something in the component, so that the rather kludgy way of resetting it doesn't have to be employed.

 

Thanks again for your help!

RandyHayes
Super User
Super User

@TedBabcock 

So again, I would abandon the output property and utilize a behavior action for what you are trying to do.

Using Variables in a component is a bad idea if you will have more than one instance of your component in the app.

At this point there is a bug in components that has gone on for too long, which is that the components share variables across instances - this includes controls in the component.  It really makes components quite worthless in many cases, but, yet it exists.

I make a lot of pop up components like you are doing and the output has never been a good one.  Turn them into behaviors and I believe you will resolve your issues.

 

Seems like you are trying to set the visibility of the component based on once they hit ok button.

If so, I'd suggest the following:

  In your app - when you want the pop up to show, set a variable to something like UpdateContext({lclShowPopup: true})

  Set the Visible property of your Popup component to : lclShowPopup

 

  Create a Behavior property in your Component called : OnOk  (set to Boolean)

  In the button or other action of the component, use set the formula to: Parent.OnOk()

 

In your app component, set the OnOk action that you now have to : UpdateContext({lclShowPopup: false})

 

You can get more mileage out of the pop up with setting the variable to a text value - the text you want to display in your popup to: UpdateContexct({lclShowPopup: "blah blah blah, press ok"})

Then, the visible property of the component to : !IsBlank(lclShowPopup)

The input property of your component for the text of your message to : lclShowPopup

And change the OnOk action to : UpdateContext({lclShowPopup: Blank()})

 

 

 

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!
TedBabcock
Advocate II
Advocate II

@RandyHayes  Yes, I guess I never did make it explicit: I'm trying to set the component's visibility with all of this. 

 

I never knew of the bug with component variables. I only have the one popup in this app, but it's good to know for the future.

 

I will set up the behaviors. One quick question: this is an experimental feature. Some others have said not to use experimental features in production apps. Do you think using behaviors in components will be okay?

 

Again, many thanks for all of your help, and for dealing with all my newbie questions, but I don't want to be given a fish, I want to learn to fish so that I can better deal with all the issues that will no doubt arise down the road. I'll report back how it goes.

TedBabcock
Advocate II
Advocate II

Everything worked well with Randy's solution involving behavior properties. Thanks!

 

To make another thing clear: the inspiration for my original attempt, comparing input and output properties, is a room in your house that has two doorways in and therefore two light switches. Whether the light is on or off is not determined by the up-down position of either light switch, but by the combination of both of them: if they're both up or both down, the light is on, and if one is up and the other is down, the light is off.

FYI or anyone having a similar problem.

I had a component (part of a Lib) with a large number of properties, with various properties referencing other properties within the same component.

Who knows why, but one of the components started throwing multiple incompatible type errors (expecting objNull).

 

There were no code/logic problems demonstrated by this sequence....  Duplicate the component, reference that component from test screen checking the component properties, all in order. Execute Lib save --> no problem. Close/reopen Lib --> duplicated component had exactly the same large number of objNull errors.

 

Relevant or not, I had used the same names for a number of property arguments for different properties and thought that might be the cause, so made sure they were all unique -->no change. 

 

The solution was to go through and use disambiguated references in formulas when calling another property. eg. funcA(parA,parB,...) with a formula of =[@parA]+[@parB]+Self.funcX([@parC]) instead of =parA+parB+Self.funcX(parC).

 

However, after doing that there was one final property with the same error (eg.funcB) not solveable by the above. I left that property, copied it to a new property (funcZ) with exactly the same formula, and changed all references (ie. all references to Self.funcB changed to Self.FuncZ) and problem solved.

 

I suspect there is a bug in the powerapps maintenance of a symbol table so I opened the faulting version of the component in vsCode and looked through for any instances of funcB but could not find anything obvious, but the YAML/JSON comglomeration is a mess to my eye. In any case, from what I can work out, the src files created by the tool are a derivative of the underlying code used by make.powerapps, not the actual execution code.

 

my 2 cents here about the pack/unpack utility: Although VB might be almost dead, exporting/importing using single VB.NET like file syntax (not executable by VS) would represent a much more usable tool for citizen developers who want to flex powerapps, than bending a markup language to express code.

Helpful resources

Announcements

Take a short Community User Survey | Help us make your experience better!

To ensure that we are providing the best possible experience for Community members, we want to hear from you!    We value your feedback! As part of our commitment to enhancing your experience, we invite you to participate in a brief 15-question survey. Your insights will help us improve our services and better serve the community.   👉 Community User Survey    Thank you for being an essential part of our community!    Power Platform Engagement Team  

Tuesday Tip | How to Get Community Support

It's time for another Tuesday Tip, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.       This Week: All About Community Support Whether you're a seasoned community veteran or just getting started, you may need a bit of help from time to time! If you need to share feedback with the Community Engagement team about the community or are looking for ways we can assist you with user groups, events, or something else, Community Support is the place to start.   Community Support is part of every one of our communities, accessible to all our community members.   Within each community's Community Support page, you'll find three distinct areas, each with a different focus to help you when you need support from us most. Power Apps: https://powerusers.microsoft.com/t5/Community-Support/ct-p/pa_community_support Power Automate: https://powerusers.microsoft.com/t5/Community-Support/ct-p/mpa_community_support Power Pages: https://powerusers.microsoft.com/t5/Community-Support/ct-p/mpp_community_support Copilot Studio: https://powerusers.microsoft.com/t5/Community-Support/ct-p/pva_community-support   Community Support Form If you need more assistance, you can reach out to the Community Team via the Community support form. Choose the type of support you require and fill in the form accordingly. We will respond to you promptly.    Thank you for being an active part of our community. Your contributions make a difference!   Best Regards, The Community Management Team

Community Roundup: A Look Back at Our Last 10 Tuesday Tips

As we continue to grow and learn together, it's important to reflect on the valuable insights we've shared. For today's #TuesdayTip, we're excited to take a moment to look back at the last 10 tips we've shared in case you missed any or want to revisit them. Thanks for your incredible support for this series--we're so glad it was able to help so many of you navigate your community experience!   Getting Started in the Community An overview of everything you need to know about navigating the community on one page!  Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Community Ranks and YOU Have you ever wondered how your fellow community members ascend the ranks within our community? We explain everything about ranks and how to achieve points so you can climb up in the rankings! Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Powering Up Your Community Profile Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile. Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Community Blogs--A Great Place to Start There's so much you'll discover in the Community Blogs, and we hope you'll check them out today!  Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Unlocking Community Achievements and Earning Badges Across the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. Check out some details on Community badges--and find out more in the detailed link at the end of the article! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Blogging in the Community Interested in blogging? Everything you need to know on writing blogs in our four communities! Get started blogging across the Power Platform communities today! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Subscriptions & Notifications We don't want you to miss a thing in the community! Read all about how to subscribe to sections of our forums and how to setup your notifications! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Getting Started with Private Messages & Macros Do you want to enhance your communication in the Community and streamline your interactions? One of the best ways to do this is to ensure you are using Private Messaging--and the ever-handy macros that are available to you as a Community member! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Community User Groups Learn everything about being part of, starting, or leading a User Group in the Power Platform Community. Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Update Your Community Profile Today! Keep your community profile up to date which is essential for staying connected and engaged with the community. Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Thank you for being an integral part of our journey.   Here's to many more Tuesday Tips as we pave the way for a brighter, more connected future! As always, watch the News & Announcements for the next set of tips, coming soon!

Calling all User Group Leaders and Super Users! Mark Your Calendars for the next Community Ambassador Call on May 9th!

This month's Community Ambassador call is on May 9th at 9a & 3p PDT. Please keep an eye out in your private messages and Teams channels for your invitation. There are lots of exciting updates coming to the Community, and we have some exclusive opportunities to share with you! As always, we'll also review regular updates for User Groups, Super Users, and share general information about what's going on in the Community.     Be sure to register & we hope to see all of you there!

April 2024 Community Newsletter

We're pleased to share the April Community Newsletter, where we highlight the latest news, product releases, upcoming events, and the amazing work of our outstanding Community members.   If you're new to the Community, please make sure to follow the latest News & Announcements and check out the Community on LinkedIn as well! It's the best way to stay up-to-date with all the news from across Microsoft Power Platform and beyond.    COMMUNITY HIGHLIGHTS   Check out the most active community members of the last month! These hardworking members are posting regularly, answering questions, kudos, and providing top solutions in their communities. We are so thankful for each of you--keep up the great work! If you hope to see your name here next month, follow these awesome community members to see what they do!   Power AppsPower AutomateCopilot StudioPower PagesWarrenBelzDeenujialexander2523ragavanrajanLaurensMManishSolankiMattJimisonLucas001AmikcapuanodanilostephenrobertOliverRodriguestimlAndrewJManikandanSFubarmmbr1606VishnuReddy1997theMacResolutionsVishalJhaveriVictorIvanidzejsrandhawahagrua33ikExpiscornovusFGuerrero1PowerAddictgulshankhuranaANBExpiscornovusprathyooSpongYeNived_Nambiardeeksha15795apangelesGochixgrantjenkinsvasu24Mfon   LATEST NEWS Business Applications Launch Event - On Demand In case you missed the Business Applications Launch Event, you can now catch up on all the announcements and watch the entire event on-demand inside Charles Lamanna's latest cloud blog.   This is your one stop shop for all the latest Copilot features across Power Platform and #Dynamics365, including first-hand looks at how companies such as Lenovo, Sonepar, Ford Motor Company, Omnicom and more are using these new capabilities in transformative ways. Click the image below to watch today!     Power Platform Community Conference 2024 is here! It's time to look forward to the next installment of the Power Platform Community Conference, which takes place this year on 18-20th September 2024 at the MGM Grand in Las Vegas!   Come and be inspired by Microsoft senior thought leaders and the engineers behind the #PowerPlatform, with Charles Lamanna, Sangya Singh, Ryan Cunningham, Kim Manis, Nirav Shah, Omar Aftab and Leon Welicki already confirmed to speak. You'll also be able to learn from industry experts and Microsoft MVPs who are dedicated to bridging the gap between humanity and technology. These include the likes of Lisa Crosbie, Victor Dantas, Kristine Kolodziejski, David Yack, Daniel Christian, Miguel Félix, and Mats Necker, with many more to be announced over the coming weeks.   Click here to watch our brand-new sizzle reel for #PPCC24 or click the image below to find out more about registration. See you in Vegas!     Power Up Program Announces New Video-Based Learning Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram. These include a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the image below to find out more!     UPCOMING EVENTS Microsoft Build - Seattle and Online - 21-23rd May 2024 Taking place on 21-23rd May 2024 both online and in Seattle, this is the perfect event to learn more about low code development, creating copilots, cloud platforms, and so much more to help you unleash the power of AI.   There's a serious wealth of talent speaking across the three days, including the likes of Satya Nadella, Amanda K. Silver, Scott Guthrie, Sarah Bird, Charles Lamanna, Miti J., Kevin Scott, Asha Sharma, Rajesh Jha, Arun Ulag, Clay Wesener, and many more.   And don't worry if you can't make it to Seattle, the event will be online and totally free to join. Click the image below to register for #MSBuild today!     European Collab Summit - Germany - 14-16th May 2024 The clock is counting down to the amazing European Collaboration Summit, which takes place in Germany May 14-16, 2024. #CollabSummit2024 is designed to provide cutting-edge insights and best practices into Power Platform, Microsoft 365, Teams, Viva, and so much more. There's a whole host of experts speakers across the three-day event, including the likes of Vesa Juvonen, Laurie Pottmeyer, Dan Holme, Mark Kashman, Dona Sarkar, Gavin Barron, Emily Mancini, Martina Grom, Ahmad Najjar, Liz Sundet, Nikki Chapple, Sara Fennah, Seb Matthews, Tobias Martin, Zoe Wilson, Fabian Williams, and many more.   Click the image below to find out more about #ECS2024 and register today!   Microsoft 365 & Power Platform Conference - Seattle - 3-7th June If you're looking to turbo boost your Power Platform skills this year, why not take a look at everything TechCon365 has to offer at the Seattle Convention Center on June 3-7, 2024.   This amazing 3-day conference (with 2 optional days of workshops) offers over 130 sessions across multiple tracks, alongside 25 workshops presented by Power Platform, Microsoft 365, Microsoft Teams, Viva, Azure, Copilot and AI experts. There's a great array of speakers, including the likes of Nirav Shah, Naomi Moneypenny, Jason Himmelstein, Heather Cook, Karuana Gatimu, Mark Kashman, Michelle Gilbert, Taiki Y., Kristi K., Nate Chamberlain, Julie Koesmarno, Daniel Glenn, Sarah Haase, Marc Windle, Amit Vasu, Joanne C Klein, Agnes Molnar, and many more.   Click the image below for more #Techcon365 intel and register today!   For more events, click the image below to visit the Microsoft Community Days website.    

Tuesday Tip | Update Your Community Profile Today!

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   We're excited to announce that updating your community profile has never been easier! Keeping your profile up to date is essential for staying connected and engaged with the community.   Check out the following Support Articles with these topics: Accessing Your Community ProfileRetrieving Your Profile URLUpdating Your Community Profile Time ZoneChanging Your Community Profile Picture (Avatar)Setting Your Date Display Preferences Click on your community link for more information: Power Apps, Power Automate, Power Pages, Copilot Studio   Thank you for being an active part of our community. Your contributions make a difference! Best Regards, The Community Management Team

Top Solution Authors
Top Kudoed Authors
Users online (2,723)