I found a bit of a rough workaround using the following (if this helps someone).
Put them on a page in this order:
- 1 label
- 1 text input
- 1 gallery
- 1 "x" icon
In terms of placement:
- Gallery is below everything
- Make a large (in height) text box, with the x icon on the right side of the text box
- Put the label in the text box.
- 1 gallery
- Do a vertical gallery on the thing you want in the combobox. Make it kinda skinny, so it looks like a dropdown.
- Items: I've got mine filtering on a collection, but you can have whatever you want.
- ONSELECT: Set(varX,ThisItem.Site); Reset('TextInput)
- Visible: Not(IsBlank('TextInput))
- 1 "x" icon (to exit the selection if you don't like it) -
- ONSELECT: Set(varX, "")
- VISIBLE: Not(IsBlank(varX))
- TEXT: varX
It ain't pretty, but I really needed a combobox...hope this helps somebody out there.
I created a workaround as well. It involves using a component. I basically created a component similar to the one that Microsoft provides in the component library demo for O365 user search.
There are some modifications, though. The data I need is in CDS, not O365. So, I use a text output on the component for the search string and a Boolean output to trigger a search. A hidden toggle control on the screen is set to the component’s Boolean output, and when that Boolean changes the OnChange property of the toggle performs a ClearCollect function to handle the search in the CDS data source. Finally, the collection itself is passed into the component as an Table Input property.
What a mess just to workaround the sizing issue with combo boxes.
Check out the on demand sessions that are available now!
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
Features releasing from October 2020 through March 2021
Una semana de contenido con +100 sesiones educativas, consultorios, +10 workshops Premium, Hackaton, EXPO, Networking Hall y mucho más!