Multidrop Down - User selected value not saving

Support
1

Hello,

Randomly as of last Friday 5/30/25 around 9am the value’s that were selected on our multidrop down have stopped being added to the value field.

The value’s are still in the dropdown, dynamically added and loaded on each form load but the user selected value is no longer being captured and saved. In order for the user to proceed to the next step, they must select a value. The forum is processing the selecting, allowing the user to move on and complete the forum as expected. It is just simply not saving that singular value in the results.

For whatever reason, this value has randomly stopped being added / saved. We did not update the forum or change any process around that time.

image
image2456×150 10.9 KB

Currently unable to determine what caused this issue nor how to fix it.

Forum: Application Field Id: DropdownMulti3

2

Hi @Locayt ,

The Dropdown multiselect options should be structured like this.

[
    [
        {
            "value": "Option 1",
            "label": null,
            "image": ""
        },
        {
            "value": "Option 2",
            "label": null,
            "image": ""
        },
        {
            "value": "Option 3",
            "label": null,
            "image": ""
        }
    ]
]

The options you are passing to Multiselect3 is structured differently, hence, when the form tries to assign the value you selected, it fails.
image

3

Hi Kenny,

Is this a recent change?

You can review our past submissions.
It’s worked nearly flawlessly until last friday 5/30/25.

4

We are experiencing a persistent issue with our form field DropdownMulti3, which is a ‘Dropdown Multiselect’ type. This field’s options are populated dynamically using an Advanced Logic Rule.

Key Context:

  • This setup was working perfectly, and selected values were being saved correctly, until approximately Friday, May 30, 2025. We made no changes to our form configuration or logic rules at the time this issue began.
  • After it stopped working, your team advised us to change our option population method from using HTMLOptionElement objects to using an array of JSON objects ({value, label, image}).
  • While the dropdown still populates correctly on the frontend with the new JSON option structure, every attempt to submit the form results in a 400 Bad Request from the API (POST .../submit/v3/ or similar).
  • The consistent error response from the server is: {\"message\":\"\\\"DropdownMulti3\\\" must receive a valid dropdown_multi value\",\"code\":\"default-error\"}.

We have tried several variations for the JSON option objects, including:

  1. { value: "Full Address String", label: "Full Address String", image: "" }
  2. { value: "Full Address String", label: null, image: "" } (to match a visual example previously seen)
  3. { value: "item_ID_0", label: "Full Address String", image: "" } (using simple, unique IDs as the value and the address as the label)

In all these cases, while the dropdown options appear correctly, the same 400 Bad Request and “must receive a valid dropdown_multi value” error occurs upon submission.

Our Questions:

  1. Platform Changes: Given that this functionality broke around May 30, 2025, without any changes on our end, could you please confirm if any platform updates or changes were deployed around that time that might have affected how ‘Dropdown Multiselect’ fields (especially those with dynamically populated options) handle data preparation for submission or how your backend API validates their values?
  2. “Valid dropdown_multi value” Definition: Could you provide the precise definition and expected JSON format for what your backend API considers a “valid dropdown_multi value” when it’s submitted? For example, if a user selects options with values “ValueA” and “ValueB”, should the submitted JSON for DropdownMulti3 be ["ValueA", "ValueB"], or some other structure?
  3. Dynamic Population Impact: Are there any known specific considerations, limitations, or best practices for ensuring that selected values from a ‘Dropdown Multiselect’ field are correctly packaged for submission when its options are populated dynamically via an Advanced Logic Rule, especially in light of potential recent platform changes?
  4. Troubleshooting Backend Rejection: What could cause the backend to reject the value for DropdownMulti3 with this specific error, even when the frontend options use simple string values (like “item_ID_0”) and are structured as {value, label, image}? Is it possible the client-side component is not packaging the selected values into the expected array format for submission?
  5. Configuration Check: Are there any specific configurations for the DropdownMulti3 field itself within the Feathery form builder (beyond its type being ‘Dropdown Multiselect’) that we should verify, which might influence how its value is processed or validated by the backend?

We are currently blocked by this issue and would appreciate your insights into what might have changed and how we can ensure our DropdownMulti3 field submits its data correctly again.

Thank you.

5

HI @Locayt ,

We recently added an additional validation to keep field values organized. This made your form field not to recognize the value when it is to be submitted, which causes the error.

We have reverted that rule since it is possibly overly strict. We apologize for the inconvenience, everything should work properly now.

6

Noted!

It works now,

Thank you!