Piping

Piping into number fields

Use an answer as a minimum, maximum or step.

Some numeric settings accept a pipe or expression as well as a fixed number. This lets an earlier answer determine a later numeric bound, for example.

Select the numeric setting's { } control to open its editor. Choose an earlier numeric answer, or enter an expression that produces a number. Fields that do not offer piping are fixed settings.

Sample answers
v:name
v:score
v:visits

Respondent sees

Calculated maximum: 8

The example shows the calculation, not a new question. Change Visits and see how the result changes.

Check the whole range

Keep the resulting minimum below the maximum and choose a compatible step. Test zero, the largest expected answer and a missing answer; a valid expression alone does not guarantee useful bounds.

Use Preview to test the actual question after changing a numeric setting. See missing answers for fallback wording and values.

Advanced piping

Essential

Add calculated expressions and pipe values into numeric fields.

Compare plans

Example: cap a follow-up at an earlier total

Ask “How many sessions did you attend?” as a Number question. A later Number question asks “How many of those sessions included a practical exercise?” Set its minimum to 0 and, where the maximum setting offers { }, insert the earlier attendance answer as its maximum.

Use a step of 1 for whole sessions. Make the source answer required if the bound always needs it, and make sure every route to the follow-up passes through that source. A required source on another branch still cannot supply an answer to someone who never sees it.

Earlier totalFollow-up to testIntended result
30Accepted as no practical sessions
33Accepted at the maximum
34Adjusted to 3 when the Number input loses focus
00Check the zero-total case and whether the question remains useful

When the result is not a usable bound

Choose a numeric answer or numeric extractor, not a choice label such as “Three sessions”. If the expression divides by another answer, handle zero before performing the division. If the question can be skipped, either route around the dependent follow-up or provide a deliberate numeric fallback.

Preview the actual input after editing the bound. The playground shows an expression result, but it does not demonstrate validation of a minimum, maximum and step together.