Unknown widget 'mendix.dropdowncontainer.DropdownContainer'.

[danlawfordMX]

When we place the widget within a table we get the following error Unknown widget 'mendix.dropdowncontainer.DropdownContainer'. When we place it outside the table the widget works as expected.

You can see the issue in this example project
MendixSupportApp.zip

[zoltanverebes]

Hi,

I experience the same problem.
I tried to use a dataview inside the list view it looks working fine this way.

[JelteMX]

@daniellawford @zoltanverebes which Mendix version are you using?

I'll see if I can reproduce it. Might be a bug in the runtime (not the widget). If so, I'll report it

[danlawfordMX]

Hi @JelteMX I was using 8.4.1.

[luisepalacios]

Hi Everyone, issue also happens on 8.5.1 happening on a custom widget also

[JelteMX]

Alright, I did a little bit of investigation. Indeed, there is some weird behavior going on with this. It looks like the table view is currently causing issues with not only this widget, but others as well. This is not specific to the dropdown widget, but the platform.

@daniellawford I am using your test-project to report this issue to R&D, thanks for providing it.

Stay tuned

[JelteMX]

As of now, I have filed a ticket and they are investigating, as this is broader than just this widget. I consider it a platform bug, but I'll wait for feedback.

I reproduced the issue in 8.2.2 as well

For now, I suggest the following:

• Do not use a table, only a layout-grid
• If you use a table and you might have a context-object that you are using (for example, in a listview), surround the dropdown with a data-view. This data-view should have the same object (you can easily do this with a Nanoflow datasource, add the object as input object and return that one. Dumb, but effective). This kind of works in my views

This is the dumbest workaround so far, but it works 😝. Quick and dirty

Nanoflow:

Table:

(If you don't have a context, you could create one with a non-persistent entity and a dataview)

[JelteMX]

Advice: Update to 8.11, it seems that some issues were found with the pluggable widgets regarding this, should be fixed now.