Dynamic, Contextual Input Options
Problem Statement:
Currently, input fields often have static, predefined options. This limits flexibility and user experience, especially when options depend on previous selections or dynamic data.
Proposed Solution:
Implement a feature that allows input fields to dynamically populate options based on:
Admin-Defined Lists:
Create and manage lists of options in the admin settings.
Assign these lists to specific input fields.
Example: A list of countries could be defined and assigned to a "Country" input field.
API-Fetched Options:
Allow input fields to fetch options from a specified API endpoint.
The API endpoint can receive parameters based on previous input values.
Example: When a user selects a "Country" from a list, the "City" input field can fetch city options for the selected country from an API.
Use Cases:
Contextual Filtering:
A user selects a "State" from a dropdown.
The "City" input field dynamically populates with cities from the selected state.
Hierarchical Data:
A user selects a "Country" from a dropdown.
The "Region" input field populates with regions within the selected country.
The "City" input field then populates with cities within the selected region.
Log in to comment and vote
Comments6
Yehoward Rudenco
Feb 22
Hey there!
I need this feature a.s.a.p!
I am making a form for my university, and I want to give the user different specialization options based on their faculty, studying cycle(bachelor or master), and different learning form. I used the logic feature, and it really makes a great UX, but it complicates my results, giving me ~50 columns of "Choose your specialization".
It wold be great if I could apply the same logic option as you apply to hide or show a block, but for the block's options.
I see it like that, depending on the results you get from different fields, you can change the options in the current field, whilst not changing the block itself.
Archie
Feb 23
Understood. This makes a lot of sense—having input options adjust dynamically based on previous selections would greatly simplify form management and improve the user experience. Your example with faculties, study cycles, and learning formats clearly illustrates the value of this approach.
Archie
Apr 10, 2025
Hi Joao,
Thank you for sharing this suggestion! We understand how useful it would be to add HTTP Request / GET validation to the Logic system for input validation. While we don’t have this feature planned at the moment, we appreciate the idea and will keep it in mind as we continue to enhance OpnForm.
Your feedback helps us improve, so thank you for contributing! 😊
Best,
Peter Kizik
Dec 18, 2024
This is very well and concisely written! However, I don’t believe this is a new ask. It has been submitted and requested countless times, and it’s even in some feature requests that have been marked as completed (by implementing custom validation but not meeting a requirement for API validation). If you feel up for it, please help bring more attention to this if you could find those feature requests and post them here with the amount of upvotes they have. I don’t feel it’s prioritized as it should be, despite how many people have been asking for this, and I suspect the issue is the technological complexity of implementing this. 😛
Julien
Dec 18, 2024
Hey guys, thanks a lot for this detailed post - and for this comment. We have other similar requests pending indeed. It is for sure something we would like to work on, but that we haven’t prioritized yet. We prefer to focus for now on features with a larger audience, that don’t require too much technical skills to use. However, we’re regularly adding features (like mentions/variables for instance) that will end up making the implementation for this easier. Finally, you’re right @Peter Kizik, this is quite challenging technically ;)
Archie
Dec 13, 2024
Hi Ennio,
Thank you for sharing this thoughtful suggestion. Adding dynamic input field options is an excellent idea that could greatly enhance flexibility and improve the user experience, especially for scenarios involving contextual or hierarchical data.
While this is not something we have immediate plans to implement, we recognize the potential value it could bring. It's a feature we might consider exploring in the future as we continue to evolve and enhance our platform. We appreciate your input and will keep this idea in mind as we plan future updates.
Best,