VMware Cloud Community
pedjono
Enthusiast
Enthusiast
Jump to solution

vRA 7.5 - XaaS dropdown list not searchable

For certain requests we need an APP ID and SQUAD ID.  This list is generated from an API, which I am simply pulling back via an action.. Returning as array of string.

When these actions are added as "External Values" to a dropdown on a “Custom Form for IaaS blueprint” it is searchable. But adding it to a XaaS form it is NOT searchable…

When I say Searchable I mean, On the IaaS I can click on the dropdown and start typing a number and it will move to items starting with that making it easy to find the right ID, but on XaaS nothing happens, making it extremely difficult for for people to select the ID for their SQUAD or APP in the list of 100's of items.

Does anyone have ideas or experience with this?

Sorry I cant provide screen shots or really much more information.

Tags (2)
Reply
0 Kudos
1 Solution

Accepted Solutions
stevedrummond
Hot Shot
Hot Shot
Jump to solution

You can very easily make it yourself for XaaS.

Make a hidden field for the values returned by your API call. Make two more string fields: filterText and selectValue.

Create an action that takes array/string and string (your ids and filter respectively). If the filter string is empty return the whole array, otherwise filter the results of the array by the string given and return those values.

Now use the predefined elements presentation binding on the selectValue field and set it to the action you just created.

Now that dropdown will show either all results or the results of the filter; the user then selects one value from the dropdown. As your API results are stored permanently in the hidden field there is no overhead in making that call repeatedly.

This also works if you need the user to select multiple values especially if you use the left/right box in XaaS for display.

I made an example for another user on this forum, I will try to find the post.

Edit: I found the post (VM Visibility - vRO / vRA ). It's not your exact scenario obviously but demonstrates the filter approach.

View solution in original post

Reply
0 Kudos
2 Replies
stevedrummond
Hot Shot
Hot Shot
Jump to solution

You can very easily make it yourself for XaaS.

Make a hidden field for the values returned by your API call. Make two more string fields: filterText and selectValue.

Create an action that takes array/string and string (your ids and filter respectively). If the filter string is empty return the whole array, otherwise filter the results of the array by the string given and return those values.

Now use the predefined elements presentation binding on the selectValue field and set it to the action you just created.

Now that dropdown will show either all results or the results of the filter; the user then selects one value from the dropdown. As your API results are stored permanently in the hidden field there is no overhead in making that call repeatedly.

This also works if you need the user to select multiple values especially if you use the left/right box in XaaS for display.

I made an example for another user on this forum, I will try to find the post.

Edit: I found the post (VM Visibility - vRO / vRA ). It's not your exact scenario obviously but demonstrates the filter approach.

Reply
0 Kudos
pedjono
Enthusiast
Enthusiast
Jump to solution

Thanks stevedrummond​, Sorry for slow reply its taken a bit to get this working..

I haven't doe this exactly as your example, but without your answer I would still be none the wiser.

I am now using the filter as per your suggestion. But rather than have a Hidden Field on the XaaS with the results to filter... I have the Action hitting the API and pulling it back and then I am filtering it.

I was struggling to get the filter to work, but after importing your package and seeing how you did it, I was away.

Though I still dont see why the drop downs on XaaS are not the same as IaaS, in being searchable.

Thanks Heaps!

Jono

Reply
0 Kudos