Multi-Select Form Fields


There is no RFC or other standard for how systems are to structure multi-select form field values in HTTP requests. While the HTML Select element is well-defined, there is nothing in either HTML or HTTP RFCs that address how to format the selected data. It’s the wild west, especially when the request’s Content-Type is application/x-www-form-urlencoded.

The request structure we see most commonly uses multiple name=value parameters, each named for the HTML element:


But we’ve also seen formats like:



Submitting Multi-Select Data to LeadConduit

For application/x-www-form-urlencoded request bodies, LeadConduit recognizes multiple name=value parameters.

String multi-select data can be captured by LeadConduit array-type or string-type flow fields. Numeric multi-select data can be captured by LeadConduit number-type flow fields.




The instances of each parameter are captured and stored as array/list elements:


Setting Acceptance Criteria

Acceptance criteria can be enforced by using an “OR” rule set with the “includes” operator. Also, numeric-type fields can be evaluated using relative-value operators. The above submit string meets all of these acceptance criteria:


Outbound Mapping

For outbound mapping of arrays/lists, array-type field elements (not string or numeric type field elements) can be individually mapped by index number.


Not specifying an index simply maps multiple instances of the parameter, each with a different index:

Outbound Mappings:


Resulting POST parameter string:


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


You must be logged in to comment.