Hi,
So, based on some answers before, I've set some dropdowns, both on a new/edit form, and a "searchy type on" to have the following for example:
"Items" property is set to:
Ungroup(Table({Item:Blank()},{Item:'[dbo].[MMMPRODUCT]'}),"Item")
Default can be set to anything (it has no affect), one idea is Blank().
What this gives me is, what I thought my client wanted:
a) Field appears "Blank" in the UI before the dropdown is selected.
b) The list of "Items" has a blank Value at the top.
I still think it's good for "editable" lists and remains the best option I've found.
But what I/he really wants is:
a) Field appears "Blank" in the UI before the dropdown is selected
BUT:
b) The list of items DOES NOT have a blank value at the top.
If you take out this bit:
{Item:Blank()}
Then I'm back to the original problem: SharePoint pointlessly assumes I want to select the FIRST value in the list, and that is what appears in the UI, before the user has selected anything!
e.g. a) Field DOES NOT appear Blank in the UI! It has a value in it! In my example, the first product in the list!
Why on earth would I want that - I can see no scenario ever where that would make sense!
Any ideas? It's not a dealbreaker for the App but it would be nice to provide a decent and sensible UI for our end users?
