@Anonymous
I just realized I never responded to your response...thanks to @KayFax for causing this to pop back up on my radar.
I hope you have figured it out at this point that the Default property does nothing on a combobox...you must use the DefaultSelectedItems property to provide a record or a table (if multi-select is enabled) to select your items.
@KayFax
If you are using Concat to store your values, then I'm assuming that the underlying column is a text column.
Also, for a combobox, Select is a record - it will be the currently selected item record (or the first is multiple are selected). SelectedItems has been around as long as the combobox has, it is a Table of all the selected records.
As for the conversion of the text value to the records for the DefaultSelectedItems property, you need to make sure you filter out any blanks.
So, for example, Filter(Split(yourTextValue, ", "), !IsBlank(Result))
This will filter out any trailing blank records.
You thought that your list of records in the Formula Editor showed all the records from the Split properly, but yet I can almost bet that there was a trailing record in that editor list that was blank...this will trip up a combobox!
But still, the key to a combobox selection is that the DSI property MUST contain records that match the Items property signature exactly...otherwise nothing will be produced.
MS is definitely pushing Dataverse, but they also are not abandoning SharePoint. This would close their market if they did as many will not pay a premium price for the dataverse on top of the existing Office 365 License. If your goal is to write one app for 1000 users to show a list of names (for example) - no one is going to pay an additional $10,000 per month just because they need a premium license to connect to Dataverse to get that list (and they don't want it in Teams). Just sayin' !
I think you might be talking about a post from Warren Belz - it is correct, sometimes datacards go bad. However, usually ONLY when the designer of the app is also mucking with the underlying datasource columns. Once you create a form, it "learns" the column types. If you then change a column type, even a refresh of the datasource in the designer will not correct the datacard...it needs to be deleted and then added back. This is usually the only issue that happens with them.
There are definitely some gotchas in PowerApps designer that will trip you up. Some will make you beat your head for a little bit, but then you learn them quickly. Things like the DataCard strangeness, the Combobox and Dropdown ghosts, Schema inferences, etc. there are a few. But...I find that most people run into these problems more when they think they are developing and doing things like a developer. If you drop the misunderstanding that you are developing and realize that you are designing an advanced Excel spreadsheet, you will not run into many of the oddities that are encountered...in other words - Keep It Super Simple and Think Excel!!
