Reporting-only variables (r9)

Reporting-only variables are hidden variables that use system resources to retrieve data in real-time, reducing the burden on surveys to retrieve and store respondent data.

To create a reporting-only variable, include the reporting only tag on coded variables, or apply the reporting only decorator to a summary variable created by the rowpunchsummary or collectionpunchsummary tags.

1. How recently have you bought the following types of snacks?
type: radio table
1. Never bought
2. More than 12 months ago
3. Between 6 and 12 months ago
4. Between 3 and 6 months ago
5. Within the last 3 months
rows:
randomize: y
1. Baked goods
2. Meat Snacks 
3. Popcorn / Crisps
4. Nuts / Dried Fruit
5. Snack bars

PURCH. Tracking snack bar purchasers
type: coded single select
reporting only: y
1. Purchaser {if anyChecked($Q715,3..5)}
2. Non-purchaser {if anyChecked($Q715,1,2)}

Details

• The reporting only tag includes translate: n by default and will not be translated or available in the Masks applet. 
• A reporting-only variable will automatically be placed after the last question referenced in the condition(s).
• To change where the reporting-only variable appears in the reporting field tree, add the report placement tag (alias reporting placement) directly on the widget. This tag accepts 'before', 'after', or 'here' as input values.
• When using 'before' or 'after' as inputs, include a question or variable ID (e.g., reporting placement: after QGENDAGE). If referencing a table, use a leading 'T' (e.g., reporting placement: before T5).

Limitations and additional information

• Reporting-only variables use system resources and store data at the system level, making them unsuitable for conditional logic or storing status or quota-related information.
• At this time, the reporting only tag is not intended to be used with loops or loop logic, or the quotas: y or click balance quota: y tags.
• Reporting-only variables cannot use list functions in the conditions being evaluated.