This issue has been plaguing me for months in different apps.
Essentially, it is always some variation of this example...
I can easily confirm this behavior by putting a label next to the combobox set to display ComboBox1.Selected. The DefaultSelectedItems shows in the combobox yet the label set to display ComboBox1.Selected remains empty until a choice is made manually.
Why is this and is there any proper workaround?
Solved! Go to Solution.
Hi @PhilD,
Could you please share a screenshot of your app's configuration?
Do you want to display the default selected value within the Combo box control in the Gallery control before interacting with the control?
Further, could you please show more details about the formula within the DefaultSelectedItems property of the Combo box control?
I have made a test and the issue is confirmed on my side. The DefaultSelectedItems property of the Combo box control is used to initialize selected item(s) before the user interacts with the control. In other words, the user does not interacts with the control.
But the Selected property and the SelectedItems property of the Combo box control is used to list the selected items resulting from user interaction. So if you don't manually select a value from the Combo box control, the ComboBox1.Selectd formula would return empty.
If you want to display the default selected value within the Combo box control in the Gallery control before interacting with the control, I afraid that there is no way to achieve your needs in PowerApps currently.
If you would like this feature to be added in PowerApps, please submit an idea to PowerApps Ideas Forum:
https://powerusers.microsoft.com/t5/PowerApps-Ideas/idb-p/PowerAppsIdeas
Best regards,
Kris
Hi PhilD,
Just curious if your SP list just plain text values, or a choices column? Might impact the final formula, but for now let's assume not. From what I understand;
My experience - When you set DefaultSelectedItems, the Selected property is also updated, but it's a complete record, so to use it in a filter or label formula you would need to specify the column of the record you want to reflect;
ComboBox.Selected.ColumnName
I'm surprised that your label is even getting updated using ComboBox.Selected when someone selects something, it should complain about needing text values while the result is a record?
Can you perhaps provide a screenshot or two to show what you're experiencing?
Kind regards,
RT
Hi @PhilD,
Could you please share a screenshot of your app's configuration?
Do you want to display the default selected value within the Combo box control in the Gallery control before interacting with the control?
Further, could you please show more details about the formula within the DefaultSelectedItems property of the Combo box control?
I have made a test and the issue is confirmed on my side. The DefaultSelectedItems property of the Combo box control is used to initialize selected item(s) before the user interacts with the control. In other words, the user does not interacts with the control.
But the Selected property and the SelectedItems property of the Combo box control is used to list the selected items resulting from user interaction. So if you don't manually select a value from the Combo box control, the ComboBox1.Selectd formula would return empty.
If you want to display the default selected value within the Combo box control in the Gallery control before interacting with the control, I afraid that there is no way to achieve your needs in PowerApps currently.
If you would like this feature to be added in PowerApps, please submit an idea to PowerApps Ideas Forum:
https://powerusers.microsoft.com/t5/PowerApps-Ideas/idb-p/PowerAppsIdeas
Best regards,
Kris
Thanks @v-xida-msft, you hit the nail on the head as far as what I was hoping to accomplish.
Combobox
DefaultSelectedItems
//set the default item to the item matching the ID in the URL query string parameter
//passed in to TextInputParameterCouncilCommittee on load [LookUp('Councils-Committees',ID=TextInputParameterCouncilCommittee.Text,CouncilCommittee)]
With this app embedded on a page, I can set the default view to show items that match the site the app is embedded on by using a URL query string parameter.
On the galleries on the first page, I work around the issue by conditionally setting the items property based on whether there is an actual selection or not. While this works, I was hoping to not have to recreate this everywhere in the app where I would like the initial value to carry through. This may be the best/only way to approach this at the moment though.
Gallery
Items
/* no item is actually "selected" in a combobox until a human picks it. this means that that setting the combobox default selected items to the URL parameter will not actually set register as selected. The workaround is to filter the galleries intially by the param value in the text box, then switch to the selected value if/when an item is chosen. */ If(IsBlank(ComboBoxCouncilCommitteeSelection_Initial.Selected.ID), Sort( // initial state Filter('Councils-Committees Applications', CouncilCommitteeID=Value(TextInputParameterCouncilCommittee.Text), MembershipStatus="Current", Role="Chair"), Name.DisplayName ,Ascending), Sort( // state when seletion is made Filter('Councils-Committees Applications', CouncilCommitteeID=ComboBoxCouncilCommitteeSelection_Initial.Selected.ID, MembershipStatus="Current", Role="Chair"), Name.DisplayName ,Ascending) )
Thanks again for your response.
This also means that the app I have using a ComboBox with items populated by the Office365SearchUser function has an issue because the Update property of the edit form must be set to something like ComboBox1.Selected.DisplayName. If a user edits the item but DOES NOT SELECT a person, then saves the form, the person field is wiped clean because ComboBox1.Selected is null (even though it is displaying the name of the current person in the field).
Currently I use this as a workaround to prevent one from actually erasing a name and making the field blank again which is better than wiping out the person field value every time someone edits another field on it.
Update property of datacard
If(Len(ComboBox1.Selected.DisplayName)=0, ThisItem.ManagerDisplayName, ComboBox1.Selected.DisplayName )
I've played a few more hours with the system and finally figure out something that works !!! Yes I get the default items selected in the combo box now!
in short, before I had this :
- Update on the data card was /Concat(ddGeo.SelectedItems, Title, "; ")/
- my DefaultSelectedItem wasI /ForAll(Split(ThisItem.Geo, "; "), Result)/
- my 'items' on the combo was /myRefList.Title/ which contains the reference list
I changed it to
- Update, Kept the same
- my DefaultSelectedItem is now /Filter(myRefList, Title in Split(ThisItem.Geo, "; ")).Title/
- my 'items' is still the same for now, I had some issues and had changed it to /Filter(myRefList, true).Title/, but doing more test with the /myRefList.Title/ seem to work
It seems that you need somehow the same kind of 'source' between defaulselecteditems and items (here a filter on the reference list)... doesn't makes much sense to me, at the end it's a list of textual value, regardless of where they come from they are the same.... anyway that fixes the issue
I still believe there's a bug in this DefaultSelectedItem ... I've done lot of testing and could see that it should work wihout without having to do the Filter, but hey...at least now it works!!
I have the same issue. I have a form setup and have a couple combo boxes set with a 'defaultseleteditems'. When saving I patch the data to a collection.
The issue I have is if a user leaves the combo boxes set to their default and saves, it patches a null value since the 'selected' property is actually blank.
I definitely consider this a bug.
Thanks @ccauser , this really helped me a lot!
I did some testing like this a while back and I'm pretty sure this approach didn't work at that time (but of course I'm not 100% sure) but this does seem to make this work now so that's all that matters really. In any event, I'm really glad you brought it back up again and took some time to figure this out. Great work, thanks!
The SelectedItems is not null in my case, my last post shows that if you use the same source for your 'items' and 'defaultselecteditems' then it works perfectly. In my case I have a myRefList which is a reference table that has the list of items (column Title) I want to display (like "A", "B", "C"), and ThisItem.Geo is a field in my main form that contains the saved previously selected items (like "A; C")
My 'items' value in the form is set with /myRefList.Title/ and what I had to change to replace defaultselecteditems from /Split(ThisItem.Geo, "; ")/ to /Filter(myRefList, Title in Split(ThisItem.Geo, "; ")).Title/
In principle both returns exactly the same thing, if I had in ThisItem.Geo the following string, "A; B", I would get in the two items "A" & "B", and in both cases I would see "A" & "B" in the combobox field as the "selected" value, but in the first case, SelectedItems would be filled with 2 nulls and clicking on the combobox would show nothing highlighted, and interacting with the combobox would give weired result, like I could select "A" again, and have in the field "A", "B", "A" !!! and in the SelectedItems Null, Null, "A". But in the second case, filtering the same source with the split, I get exactly what it should be, field shows the 2 values, selected shows the 2 values, the combobox shows the right highlighted value and user interaction would work as expected.
My point on this still being a bug, is that by just entering "A" as a defaultselecteditems, as the combobox contains string, should do the right things rather than to have to filter the source to return the "A" string from the source
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!
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
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.
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