Impossible to use dynamic search in form using Row component

Feature(s) impacted

addAction and dropdown field with dynamic search (nodejs agent)

Observed behavior

Dropdown with “dynamic” search doesn’t work when Row layout is used in the form.

This simple Action Form display correctly in the GUI, but when I type something to search in the field dropdownWithDynamicSearch I got a console error (see below) and options function is never called.

If I remove the Row component, everything works good

        collection.addAction("Test bug", {
            scope: "Global",
            execute: () => {},
            form: [
                {
                    component: "Row",
                    type: "Layout",
                    fields: [
                        {
                            label: "anyOtherField",
                            type: "String",
                        },
                    ],
                },
                {
                    id: "dropdownWithDynamicSearch",
                    label: "Test",
                    type: "String",
                    widget: "Dropdown",
                    search: "dynamic",
                    options: async (context, search) => {
                           // async query never called
                    },
                },
            ],
        });

Expected behavior

The options function must me called and options must be displayed

Failure Logs

Context

  • Project name: waro
  • Environment name: production
  • Agent technology: nodejs@1.47.0
  • Database type: MySQL
  • Recent changes made on your end if any: update from 1.43.0 to 1.47.0 and add row in Action Form

Hello @alvex,

Indeed, there is an issue on this new feature. Thanks for the report, I have reproduced it.
We are currently working on a fix to resolve it and will keep this thread updated.

@Nicolas.M

Hello,

We just released a fix to the agent.
Please upgrade your agent to latest version, and let us know if this fixes your issue :pray:

@Nicolas.M

1 Like

Hello,

I tested it on a dev branch and it seems to work, thank you for the quick fix :slightly_smiling_face:

Best,
Alexandre

2 Likes