DropdownTags (OutSystems UI, Reactive) bugs: empty itemlist hides field, wrong labels

We're using the DropdownTags component in a Reactive web app and are finding multiple problems with it.

I've attached a project showing these problems/bugs in detail.

Bug #1\: Duplicate entries after data refresh (Note: Should be solved in next version of OutSystemsUI, see this forum post)

Bug #2\: Empty item list does not render the field.

A DropdownTags component with an empty ItemList does not render the field. This is not the normal behaviour for the Choices Javascript component that DropdownTags uses (I tried), but seems to be an OutSystems specific problem.

Bug #3\: Empty item list does not render the field (2) -> "Cannot read property 'destroy' of null".

As explained in Bug #2, a DropdownTags component with an empty ItemList does not render.  This becomes very clear when navigating to another page.  Then OutSystems tries to call the destroy() method on this unrendered field ans shows an error.

Bug #4\: Unwanted (and wrong) labels.

Having multiple Dropdowntags on the same page forces the same label on ALL DropdownTags fields (event the hidden one! (see bug #2)).  OutSystems (or Choices) seems to show a label only if the label is different from the search prompt.   Setting the search prompt forces the same label on ALL DropdownTags. 

Please see the example application in attachment for a more detailed explanation and example of these problems/bugs.


Hi Steven,


The forums is not really the place to submit bugs. If you have a bug/support request - your best option is to open a support ticket. That way things will get routed to the correct teams. 


Thanks,


Stacey