dynamic
property on the inputFields
object. The value for the property is a dot-separated string concatenation.
hidden: true
on it’s display object.
New Records
trigger with Spreadsheet
and Worksheet
dynamic dropdown input fields, which have keys spreadsheet_id
and worksheet_id
respectively. The selected spreadsheet value is available via bundle.inputData.spreadsheet_id
to be used by the Worksheet
trigger.
Note: Be mindful that a dynamic dropdown can depend on the value chosen in another dynamic dropdown. Two types of dependencies can exist between fields: Requirement dependency: Affects how dependent fields are enabled or disabled within the UIValue dependency: Affects how dynamic dropdown field options are retrieved
- Setting
required: false
makes a field optional and always enabled in the UI.- Having no required value set makes a field optional and disabled until the dependencies are selected.
So, if you have an optional dynamic dropdown that depends on another dropdown input field, that field should not have
- Setting a required value or not does not affect how the options of a dynamic field are retrieved.
required: false
set. Input fields are optional by default, but settingrequired: false
on an optional dynamic dropdown field that depends on another removes the requirement dependency relationship. In the example above, theworksheet_id
input field will be disabled until thespreadsheet_id
input field has a value in Zapier’s products such as the Zap editor. Notice that settingaltersDynamicFields: true
signifies other input fields need to be recomputed whenever the value of that field changes.
bundle.meta.isFillingDynamicDropdown
. This can be useful if need to make use of pagination in the dynamic dropdown to load more options.
search
with a value of <searchActionKey>.<outputFieldKey>
.
<searchActionKey>
with the key
of the search action that should prepeded to the user’s workflow.<outputFieldKey>
with the key
of the output field from that search action that should be mapped as value for the input field.