freeform

Blocks are commonly used for programming questions that repeat in a "loop." By default, blocks assume each iteration is related to others, allowing questions/variables to be summarized in a single "rollup" (summary) tile or row in reports. This simplifies data interpretation by requiring similar characteristics across iterations, like question type and response options.

For blocks that don't fit this summary model, add freeform: y to the block definition. This ensures the software treats each iteration uniquely, without summarizing them in a rollup tile/row.

MODULE. QUOTA | Select up to two modules on a least filled basis
type: quotas
maxgroups: 2
1. Accounting
2. Assurance
3. Advisory
4. Tax

setlist: SERVICES
order: [*]
1. Accounting 
2. Assurance 
3. Advisory
4. Tax

block: <<ENDLOOP

4X%%ID%%. Please answer the following statements as they relate to the ease of procurement of additional modules from your <b>%%TEXT%%</b> provider.
type: checkboxtable
instruct: Please select all that apply
1. Decision makers are similar across modules
2. Modules have a high degree of data and expertise overlap
3. The billing structures are compatible across modules
4. Having a single point of contact across these modules is highly valuable
5. There are no meaningful benefits to purchasing these modules from the same service provider
rowsfrom: SERVICES -[%%ID%%]
ENDLOOP
freeform: y
list: QMODULE

In the example above, each question iteration presents a different set of options to the respondent. For instance, if a respondent is assigned "Accounting" and "Tax" at QMODULE, Q4X will be asked twice: once for Accounting and once for Tax.

• Q4X1, for Accounting, uses the SERVICES list but excludes the "Accounting" option.
• Q4X4, for Tax, also uses the SERVICES list but excludes the "Tax" option.

Since the row option IDs differ, the block won't parse correctly without the freeform tag.