Forum Discussion
MicrosoftSet values for Managed Metadata (aka Taxonomy) columns in PowerApps and Flow! (First Release)
We've encountered an issue where the list of Terms is cut off prematurely:
We have a full list of countries which stops at Bhutan, the user can search for other countries and they appear just fine. This is a multi-select field.
Any advice?
- I'm having the same issue - have you found a workaround or way to increase the number of items displayed?
- Kerem Yuceturk
Hi Liam Harrison, Angela Engelbrecht, sorry about the inconvenience. We are limited to showing 20 items but we will keep bringing up items that match as the user types in. Is there a reason you want to show more than 20 items at a time? We figured users wouldn't need to scroll among that many items.
We can try to get the number bumped up to a higher value like 50 at a time, would that help your scenarios?
Kerem Yuceturk - thank you for your response.
The term set I am referencing has a list of all services and sub services offered. Because there is no way of representing the hierarchy we are now seeing a flat list of all services. Not all users are aware of all the services offered. In the older list form they would click the tags (icon) to view all the terms in the set .
Increasing the number of items to scroll would possibly resolve the issue for now however if this list of services grows we may run into the same issue again. Users may end up selecting a close match instead of the correct one as it wasn't visible at the time.
Thanks again,
Angela
- Kerem Yuceturk
There is a trick Angela Engelbrecht that might help.
In your form, you can choose to display the path of the item, alongside the label of it. To do this:
1. Select the combo box control displaying your managed metadata field
2. In the properties tab, click on the data source name, next to "Data"
3. In the panel that opens, change the layout from Single to Double
4. This adds a secondary text field, in which you can display the path of the items.
Thanks Kerem Yuceturk,
I can see why the limitation is there but for this particular scenario I don't think it would help unless you could push it up to 500 or so.
Perhaps another way to look at it is from the users' point of view. Imagine I need to put United Kingdom as my country. It's a bit of a jarring experience if I'm filling out a form, I get a drop down box and the country I'm looking for just isn't there. The fact that there's a drop down implies that that's the best way to interact with this field, but it's not in this instance. It would be better if I only had the option to type/search or if I was prompted to access multiple pages of results if I wanted to browse. Both these options would help me get to the value I want.
As it stands I come to the field, hit the limit and that's it, there is no indication that I could search instead. So if I'm expecting to browse to the value I have no idea what to do next.
- Kerem Yuceturk
Liam Harrison, agreed the default text doesn't give enough of an indication.
Maybe as a workaround, you can type in some other text into the InputTextPlaceholder property to say "Type to see more options" or something similar (see picture below). Going up to 500 items is probably not feasible for performance reasons, and it is too many items to scroll through for a user as well.
Hi Kerem Yuceturk,
I have built a PowerApp that is not directly connected to a SharePoint list. However, I have created a list with the MMD field to serve as input into my PowerApp. The MMD fields are being surfaced as drop-down lists with no option to type the values. Therefore, displaying a higher number, such as 50 would definitely help. When could we expect this?
Thanks,
-Haniel
