We would like the ability to dynamically populate dropdown options in a Chains Runtime Inputs trigger.

Currently, dropdown options must be manually defined and maintained in the chain. Our use case is to run an Oracle OTBI report that returns the current valid list of values and use those results as the available options in a Runtime Input dropdown.

Ideally, the dropdown could use one of the following as its data source:

• A Wdata table or query
• The output of another chain
• A workspace resource or CSV file
• An API or connector response

The list should also support configurable display and return values. For example, the user could see:

October 2026 - Open

while the chain receives:

OCT-26

Each user should receive their own private Runtime Inputs form when executing the chain. User selections should not be stored in or displayed through a shared spreadsheet or control sheet.

Business impact

Our Oracle list of valid values changes over time. Hardcoding the values in the chain requires ongoing maintenance and creates a risk that users select outdated or invalid values. A shared Workiva control sheet is not an appropriate alternative because multiple users may be submitting requests concurrently and should not see or overwrite one another’s selections.

Requested functionality

1. Allow a Runtime Input dropdown to use a dynamic data source.
2. Support separate display labels and returned values.
3. Refresh the options on a schedule or when the form opens.
4. Preserve the current per-execution privacy of Runtime Inputs.
5. Optionally support searchable and dependent dropdowns.

This would allow Chains Runtime Inputs to function as a secure, lightweight request form without requiring Power Apps, SharePoint, or another external form platform.