cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
jed76
Post Prodigy
Post Prodigy

ComboBox IsEmpty not working?

I can't understand what I'm doing wrong here:

 

I'd like a ComboBox to either be visible or not (or I could use DisplayMode.Edit / DisplayMode.View) if another ComboBox is empty. However, it doesn't seem to work and even when I use:

 

If(!IsEmpty(ComboBox1.Selected),DisplayMode.View,DisplayMode.Edit) for the DisplayMode of the other ComboBox, it still seems to think that there is some content in the ComboBox even when it is actually blank / empty? This means the other ComboBox remains in VIEW mode even when the other box is blank?

1 ACCEPTED SOLUTION

Accepted Solutions

@jed76 

@poweractivate 

 

.Selected is VERY viable on a ComboBox.  It is not Deprecated.  I believe you are thinking of SelectedText which IS deprecated and should be avoided.

 

But, Selected is absolutely usable and HAS to be used in many cases.  If you want to know what item is selected in your ComboBox...how else would you do it?  That is what .Selected is for.

 

Selected returns the selected record in your ComboBox.

SelectedItems returns the table of records selected IF you have multiple selections turned on.

 

DefaultSelectedItems is an input property to the combobox, so you cannot check it in a formula.

 

Like ALL controls that have an Items property as an Input, any output will present either a record or a table of records based on the schema of the Items property records.

 

SO...whatever columns you have in your Items property are what you would check in your formula.

The column you check is completely dependent on the schema of the Items property records!

 

If you had an Items property that was just ["A", "B", "C"] then this would represent a table with a Value column...and then Selected.Value would be what to check.

 

@jed76 

Your original formula is using IsEmpty.  This function is well misunderstood as it is a function to test if a record or table is empty.  And by empty, I mean nothing!

For example:  IsEmpty(Table()) is true whereas IsEmpty(Table({})) is false

This is because the second one has a record in it.  Technically it is all empty (to us), but to the IsEmpty function, it has something and is not empty.

So, when trying to do the IsEmpty function on a schema based table that is found in a SelectedItems it will always return false

Bottom-line...it is NOT the function you want to use to test with in this case.

 

IsBlank is what you want!

 

Your formula should be:

If(!IsBlank(ComboBox1.Selected.Value), DisplayMode.View, DisplayMode.Edit)

(using the .Value here based on prior comments...again, replace with the appropriate column from your items schema)

 

You could also use:

If(CountRows(ComboBox1.SelectedItems)>0, DisplayMode.View, DisplayMode.Edit)

 

Note, the first is looking at a record from the combobox.  Selected will ALWAYS represent the record of the last selected item of the control.  

SelectedItems is used in the second formula in which case (again, IsEmpty will not work on it) we use the CountRows to countrows of the table.

 

Hopefully this all makes sense and is helpful.

 

 

_____________________________________________________________________________________
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

30 REPLIES 30
poweractivate
Most Valuable Professional
Most Valuable Professional

@jed76 

 

You should not use Selected for ComboBox

 

use SelectedItems instead, and do not use the Selected property of a Combo Box control, if possible

 

Try this instead:

 

//untested - adjust as needed
If(!IsEmpty(ComboBox1.SelectedItems),DisplayMode.View,DisplayMode.Edit)

 

 

or this (but the above is better):

 

//untested - adjust as needed
If(!IsBlank(First(ComboBox1.SelectedItems)),DisplayMode.View,DisplayMode.Edit)

 

 

Also, note:

 

IsEmpty is for a Table

IsBlank is for a single Record

 

and you should not use Selected property for ComboBox

use SelectedItems property instead for ComboBox

 

------------

NOTE:

Although the below may still work with Selected, I do not recommend it and I think it is deprecated

Spoiler
//DO NOT USE THIS, NOT RECOMMENDED
If(!IsBlank(ComboBox1.Selected),DisplayMode.View,DisplayMode.Edit)
//don't use it - this might stop working in the future
//and you shouldn't use the Selected property of a ComboBox
//use SelectedItems or DefaultSelectedItems instead

I do not recommend using Selected property of ComboBox, I think it is actually deprecated and may stop working in the future

 

poweractivate
Most Valuable Professional
Most Valuable Professional

@jed76 

 

Don't use Selected for a ComboBox.

Use either DefaultSelectedItems or SelectedItems

 

In your case, you probably want SelectedItems

 

see if it helps @jed76 

@jed76 

@poweractivate 

 

.Selected is VERY viable on a ComboBox.  It is not Deprecated.  I believe you are thinking of SelectedText which IS deprecated and should be avoided.

 

But, Selected is absolutely usable and HAS to be used in many cases.  If you want to know what item is selected in your ComboBox...how else would you do it?  That is what .Selected is for.

 

Selected returns the selected record in your ComboBox.

SelectedItems returns the table of records selected IF you have multiple selections turned on.

 

DefaultSelectedItems is an input property to the combobox, so you cannot check it in a formula.

 

Like ALL controls that have an Items property as an Input, any output will present either a record or a table of records based on the schema of the Items property records.

 

SO...whatever columns you have in your Items property are what you would check in your formula.

The column you check is completely dependent on the schema of the Items property records!

 

If you had an Items property that was just ["A", "B", "C"] then this would represent a table with a Value column...and then Selected.Value would be what to check.

 

@jed76 

Your original formula is using IsEmpty.  This function is well misunderstood as it is a function to test if a record or table is empty.  And by empty, I mean nothing!

For example:  IsEmpty(Table()) is true whereas IsEmpty(Table({})) is false

This is because the second one has a record in it.  Technically it is all empty (to us), but to the IsEmpty function, it has something and is not empty.

So, when trying to do the IsEmpty function on a schema based table that is found in a SelectedItems it will always return false

Bottom-line...it is NOT the function you want to use to test with in this case.

 

IsBlank is what you want!

 

Your formula should be:

If(!IsBlank(ComboBox1.Selected.Value), DisplayMode.View, DisplayMode.Edit)

(using the .Value here based on prior comments...again, replace with the appropriate column from your items schema)

 

You could also use:

If(CountRows(ComboBox1.SelectedItems)>0, DisplayMode.View, DisplayMode.Edit)

 

Note, the first is looking at a record from the combobox.  Selected will ALWAYS represent the record of the last selected item of the control.  

SelectedItems is used in the second formula in which case (again, IsEmpty will not work on it) we use the CountRows to countrows of the table.

 

Hopefully this all makes sense and is helpful.

 

 

_____________________________________________________________________________________
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!
jed76
Post Prodigy
Post Prodigy

@RandyHayes 

 

As always - a thorough and very helpful response. Thank you very much! I’ll give your suggestions a try.

 

Thank you!!

poweractivate
Most Valuable Professional
Most Valuable Professional

@RandyHayes 

 

I really like this explanation, however I was still not sure whether or not the Selected property of a Combo Box control in particular, might be internally scheduled for eventual future deprecation

and if so that it should not be used, and here is why I might suspect this:

 

Since there are cases where a Combo Box may allow multiple selections, then using the Selected property would be ambiguous, because it would result in only one Record (when I checked, it works, but it picked the very last selection, though I am not sure exactly what selection it picks, whether it's the first one, last one, or even just arbitrary). In this case, the expected behavior might be for it to get all the Records, in some points of view.

 

That's not what I necessarily think the expected behavior of Selected should be, I think it's behaving fine.

 

However, if someone were to use that property Selected for a Combo Box in particular, they might get confused about the behavior of why only one Record is being returned and not a Table. In other words, perhaps some people might wonder, why is there a property Selected of a Combo Box which returns just one Record, when a Combo Box may have one or more Records - and if there are multiple records, how are they supposed know which of the selections will be chosen if they use the Selected property of a Combo Box?

 

The obvious answer is not to use Selected when your Combo Box allows multiple selections, as it would result in an unexpected outcome. 

 

However, SelectedItems can be used predictably and consistently with a Combo Box control in both cases - with one selection, or multiple selections.

 

Instead, whether it's only one Record or multiple Records, SelectedItems is more consistent. When there's only one Record, then just use

 

//example formula - change ComboBoxControl to the actual name of your Combo Box control
First(ComboBoxControl.SelectedItems)

 

When the destination requires a Record and not a Table, they should get an error in the formula, so they will have to change the formula to use only one of the Combo Box selections explicitly, such as by using First.

 

However, Selected will not give any error, it will just pick one of the multiple selections. Some people may wonder, why would there be a property which would have an unexpected outcome in the case of multiple selections? Also, some people may wonder, Selected returns only one Record - does that mean - a Combo Box always returns one Record too? It might introduce ambiguity in even what a Combo Box is and whether it returns one Record or a Table from some points of view.

 

I personally don't really have an issue with this, however, I believe that in some points of view, this type of situation is considered problematic, specifically that: when multiple Records are expected from a Combo Box (i.e. a Table) why is there a built in property that returns just one of them (i.e. a Record), whether it's the first one, last one, or an arbitrary one?

 

I also noticed that the property Selected of a Combo Box control is missing entirely from the relevant official Microsoft documentation page.

In case this was not a mistake, it may mean that the property is internally being scheduled for eventual deprecation. I am aware it could be a mistake, however, I am actually unsure it is a mistake in this case, I think there is a chance that the Selected property of a Combo Box might be intentionally missing from the documentation in this case.

 

I suspect it could be because of what I described, and thus, the Selected property of a Combo Box control in particular might be internally scheduled for eventual deprecation for the reasons I described in this post.

 

The use of property Selected is not consistent with the principle that while a Combo Box may have only one selection, and often does in many cases, (such as when the SharePoint List data source's Choice column  does not have Allow multiple selections toggled to Yes in the settings, and the default setting if not explicitly changed, is indeed No, so often it's just one selection in the Combo Box control that uses this column) but that it may also have multiple selections in some cases.

 

The Selected property on a Combo Box control introduces ambiguity on what Record is returned in the case that the Combo Box does have multiple selections. 

 

I wanted to know if @v-jefferni , @v-bofeng-msft , or @v-xiaochen-msft could please clarify on this. Specifically, to clarify on:

 

1. Is it a mistake or is it intentional that the property Selected of a Combo Box control is missing entirely from the relevant official Microsoft documentation page

 

2. If it is intentional that the property Selected of a Combo Box control is missing from that page, is it because the Selected property of a Combo Box  might be internally scheduled for eventual future deprecation?

 

3. If the Selected property of a Combo Box  might be internally scheduled for eventual future deprecation, might it be partially because of what I just described in this post, potentially among other reasons?

 

4. If the Selected property of a Combo Box  might be internally scheduled for eventual future deprecationdespite what @RandyHayes says being a very strong explanation (I really like it a lot personally), that maybe it is actually not a good idea to be encouraging anyone to continue to use the Selected property of a Combo Box and in that case, would it be better to go with my advice instead to simply not use the Selected property of a Combo Box and instead to use SelectedItems in all such cases, even for returning just one Record ?

So:

 

//example formula - change ComboBoxControl to the actual name of your Combo Box control
First(ComboBoxControl.SelectedItems)

 

for cases where it is known that there is going to be only one selected item in the Combo Box?

 

5. If it actually was a mistake that the Selected property of a Combo Box control is missing from that page, could it be clarified which Record is returned exactly, when using the  Selected property of a Combo Box control that allows multiple selections - is it always the first Record, the last Record, or is it not predictable at all which Record is returned?

 

I wanted to know if the above could be clarified so I could have the correct understanding.

 

Thanks!

@RandyHayes  Just tried this and it works a treat.....

 

*****IGNORE - I have just figured it out by using an OR statement set to check for "ThisItem.<columnName" !IsEmpty as well. Many thanks. *******

 

However. When the gallery writes back to the SP list, I have the ComboBox's Default Selected Items to show "ThisItem.<Column Name in SP List>". How can I also use this value as well so that the other ComboBox is in VIEW mode only? For example, when I am populating the boxes, it works a treat. However, when I return the gallery after the items have been patched back to the SP list, the combobox returns a FALSE again since it is now displaying its default seleced item, if you see what I mean?

 

Many thanks. 

@jed76 


@jed76 wrote:

... when I return the gallery after the items have been patched back to the SP list, the combobox returns a FALSE again since it is now displaying its default seleced item, if you see what I mean?

 

Many thanks. 


For that check if below two threads help you identify this potential specific issue:

Combo box auto populated data not working with Patch or in email

Combo Box Selected Items - Lookup Field Issues 

 

 

poweractivate
Most Valuable Professional
Most Valuable Professional

@jed76 

 

First, check your Form's Item property (if it's a Form). Is it set to the Record you want?

If it's not a Form, or if you are sure it is correct, then:

 

Check the Gallery you are referring to. Do you mean that the Combo Box is a Control that is inside the Gallery? If so, check the DisplayMode of the Combo Box - is it set to DisplayMode.View? Whether it is or not though, a value should still be populating in there if you have  DefaultSelectedItems correctly set of that same Combo Box (which it seems like you do to me).

 

Otherwise, you have already indicated that you might have DefaultSelectedItems correctly set

(but check it once more just in case).

and if so,

Check those two threads I gave

especially the first one Combo box auto populated data not working with Patch or in email  

as that may help you identify your issue.

 

See if it helps @jed76 


@jed76 wrote:

@RandyHayes  Just tried this and it works a treat.....

 

*****IGNORE - I have just figured it out by using an OR statement set to check for "ThisItem.<columnName" !IsEmpty as well. Many thanks. *******

I see you might have resolved your issue now, glad you were able to resolve it 🙂

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

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