[ Components ] Add "Other" Option Toggle to Multioptions Component

[NDCallahan]

🧩 Feature: Add "Other" Option Toggle to Multioptions Component

📝 Description

When using the Multioptions component in Budibase, developers often want to give form fillers the flexibility to provide a custom response if none of the predefined options apply. Currently, there’s no built-in way to support an “Other” option that reveals a text input when selected.

This feature proposes adding a toggle to the Multioptions component that enables an “Other” option. When selected by the user, a text box would appear directly beneath it, allowing the form filler to enter a custom response. This pattern is widely used in forms and surveys to improve accessibility and completeness of data collection.

💡 Use Case

As a Budibase user, I want to enable an “Other” option in Multioptions so that form fillers can:

• Provide a custom answer when none of the predefined choices apply.
• Avoid abandoning the form due to limited options.
• Ensure edge cases and unique responses are captured without needing to redesign the form.

✅ Expected Behavior

• A toggle in the Multioptions component settings labeled “Enable ‘Other’ option”.
• When enabled:
  • An “Other” option appears at the bottom of the list.
  • Selecting “Other” reveals a text input field directly beneath it.
  • The entered value is stored alongside or in place of the selected option.
• Works in both single-select and multi-select modes.
• Fully compatible with form submission logic and data binding.

🚀 Why It Matters

• Improves flexibility and inclusivity in form design.
• Reduces friction for users who don’t see their answer listed.
• Aligns Budibase with standard UX patterns used in surveys, onboarding flows, and feedback forms.
• Eliminates the need for custom workarounds or conditional logic to simulate this behavior.

🌍 Forms Platform Precedents

• Typeform and Google Forms both support “Other” options with conditional text inputs.
• Jotform also includes built-in support for “Other” responses in dropdowns and radio groups.
• SurveyJS includes “Other” response handling for multiple choice components.
• These platforms demonstrate that “Other” is a widely adopted pattern for user-friendly data collection.

🖼️ Screenshot

Current

Future

[linear[bot]]

BUDI-9943

[mikesealey]

Hey @NDCallahan

Currently, there’s no built-in way to support an “Other” option that reveals a text input when selected

it's not necessary to make a code-change for this. You should add the form-field you need underneath your Options picker or Multi-select picker, and use "Conditions" to show the field if the "Other, please specify" option is selected, and update the validaiton to Required.

Example:

Nates workspace-export-1764668067646.tar.gz

[NDCallahan]

While there are multiple ways to capture custom input, introducing a built-in “Other” option within the Multioptions component would significantly improve clarity, consistency, and data hygiene from the end user’s perspective.

This isn’t just about developer convenience — it’s about aligning Budibase with common UX patterns seen across leading form platforms. Allowing users to select “Other” and enter a custom response directly within the component ensures:
• Cleaner data collection without fragmented workarounds.
• A more intuitive experience for form fillers who don’t see their answer listed.
• Consistency across forms, especially when reused or scaled.

As developers, we can simulate this behavior manually, but doing so introduces unnecessary complexity and inconsistency. Most modern form builders — including Typeform, Google Forms, Jotform, and SurveyJS — treat this as a standard feature. Budibase should too.