Multi-Value Fields

Some data source fields store several values in a single text cell, separated by a delimiter such as a comma (Health, Dental, Retirement) or a semicolon (Health;Dental;Retirement). Multi-Value Fields lets you mark a text field as a list and tell Streamline which delimiter to split on. Once configured, the field can be mapped to prefill Form checkboxes, render cleanly in Documents, and write the list back to the data source with the correct separator.

Who Has Access?

Key Capabilities

Mark a text field as a list: Designate any text data source field as a multi-value field and define its separator.

Prefill Form checkbox with data source: Form checkboxes prefill the matching options automatically at run time.

Form to Deliver Data write-back: Write the selected list back to a multi-value target field. The same behavior works inside repeating records.

SUpported in Documents: Render mapped checkbox and radio fields as text or as visual checkbox or radio controls.

How to Use Multi-Value Fields

Using Multi-Value Fields is a two-part process: configure the field in the Data Catalog, build the workflow that uses it, then run the workflow to prefill, collect, and write back the list.

Part 1: Configure a Field as Multiple Values

You configure Multiple values on the data source field, before you map that field in a workflow.

1. In the Streamline navigation bar, click Data Catalog and select the data source and entity that contains the text field.
2. In the entity's field list, open the text field you want to treat as a list. The field must be a String type - non-string fields show a message explaining that Multiple values is not available for that field type.
3. Open the Multiple values configuration.
4. Turn on the Enabled toggle. The separator field becomes available.
5. In the Enter a separator field, type the exact characters that separate values in your data source. You can enter up to 5 characters, and spaces are allowed.
   • For values like Health, Dental, enter , (comma + space).
   • For values like Health;Dental, enter ;.
   • For values like Health; Dental, enter ; (semicolon + space).
6. Click Apply to save the configuration. To turn the feature off later, open the modal and click Disable. This does not change the data in your data source; it only stops Streamline from splitting and joining.

Important: Turn on Multiple values before you add or map this field in a workflow. If the field is already mapped when you enable Multiple values, Streamline still treats it as plain text. See Feature Considerations for the re-map fix.

Part 2: Set Up the Workflow

Once the field is configured, build the workflow that uses it. The steps below cover Data Search to From and Document prefill mapping and data delivery back to the data source.

Step 1: Search Data step

1. Add a Search data step to your workflow.
2. Configure the search to return the field you configured as Multiple values. Streamline returns it as a list (array of strings), not a single string.

Note: You cannot filter on a multi-value field in Data Search. Use another field to find the record; the multi-value field can still be returned and mapped downstream.

Step 2: Add a Form step with checkboxes

1. Add a Form step.
2. Add a checkbox field to the form.
3. Make sure the checkbox option labels match the stored values exactly, including spelling and case.
4. Map the Search field to the checkbox.

   Important: If you mapped this field to the form before turning on Multiple values, remove the mapping and add it again. The field type changed from a single string to a list, and the existing mapping still points at the old type.

Step 3: Add a Deliver Data step

1. Add a Deliver data step that targets a multi-value text field.
2. Map the Form checkbox to that target field.
3. On create or update, Streamline joins the list with the target field's separator and writes it.

Step 4: Add a Document step

1. Add a Document step and map the checkbox (or radio) field into the template.
2. In the field's settings, use the Display as dropdown to choose how the field renders:
   • Checkbox - shows the values as the visual checkbox control, with each option label listed.
   • Text - shows all selected values as a comma-separated text string (for example, Option 2, Option 3).
3. For each option, enter the Option value (the stored value) and manually type the label you want displayed in the document.

Tip: A single document can show the same multi-value field both ways, checkbox controls or as text, so you can present the data in the format each part of your document needs.

Feature Considerations

Configuration order matters:

• If you turn on Multiple values after a field is already mapped in a workflow, Streamline still treats the field as plain text. Remove the field from the step or mapping and add it again (re-map) after Multiple values is saved.

Salesforce multipicklists are not auto-detected:

• Streamline does not automatically recognize Salesforce multipicklist fields as multi-value. Configure Multiple values manually on the field and set the separator to ;.

You cannot filter on a multi-value field in Data Search:

• Use another field to find the record. Multi-value fields can still be returned and mapped downstream.

The separator must match the data source exactly:

• A wrong separator produces wrong splits or a failed write-back. Include spaces if your data uses them (for example, , not ,).

Values that contain the separator cannot be written:

• If a selected value itself contains the separator character, delivery fails with a clear error. Escaping and quoting are not supported. Remove the separator from the source value, or choose a separator that does not appear inside any value.

Checkbox options must match stored values exactly:

• Matching is case-sensitive. Health is not the same as health.

Text lists only:

• Multiple values supports text fields only. Numbers, dates, and booleans are not supported as lists in this release.

Webhook arrays are not supported as multi-value:

• Multi-value handling applies to data source text fields. Webhook arrays are not treated as multi-value in this release.

Order is not preserved:

• The order of values in the list is not guaranteed to match the order in the source or the order selected in the form.

List to single-text mapping is unchanged:

• Mapping a list to a normal single-text field still joins the values with ", " (comma + space). The target separator only applies when the destination field is itself configured as Multiple values.

Troubleshooting