datatype

The 'decimal' datatype dictates the number of decimal places a response can contain. A single value specifies that the response must contain that many digits after a decimal. For example, Q1A will only accept a response that goes out two decimal places.

Ranges can be specified with two values, e.g., '1-2', or a single value with a hyphen, e.g., '-2'. The former (as shown in Q1B) indicates the respondent can enter a number with one to two decimal places, whereas the input in Q1C indicates they can enter up to two decimal places.

See demo See code Restart demo

The type: date question type automatically requires responses in a mm/dd/yyyy format. If the date is selected from the calendar pop up instead of manually entering a response, the selection will automatically fit this format. To require a different format, include one of the date datatypes.

Q3 uses the 'date_mmddyy' datatype to require a two-digit year. Q4 meanwhile uses the 'date_ddmmyy' datatype, listing the day before the month. The start date and end date tags are also included to restrict the date range that can be entered or selected from the calendar pop up.

See demo See code Restart demo

The start table widget is useful for defining more complex tables such as multicolumn or multitype tables. In the example below, though each row requires a text response, rows 2 and 3 use different data types. To define each row independently, we include a full line space between them.

Both 'phone' and 'email' have built-in text field sizes (18 and 25 ems, respectively), but a size tag could be added to each row's definition to override this if need be. These datatypes are also encrypted automatically, so only those with a Superuser system role will be able to see data for those fields.

See demo See code Restart demo

The 'phone' datatype allows for three input lengths: 5, 7, and 10 digit numbers. As such, validations are necessary to force a 10 digit response. In Q6, the validation uses regex so respondents can only enter a 10 digit number while still allowing variations in formatting. Using hyphens or parentheses around the area code are optional, but spaces are not permitted.

See demo See code Restart demo

cvalue: $QX =~ s/\D+//gr

It is extremely rare that clients need the full UK postcode, as the first part (the out-code) and the first number of the second part (the in-code) are already accurate enough for consumer market research purposes. 

Full UK postcode

The 'ukpostcode' datatype will capture the full UK postcode.

7. What is your full postcode?
preface: THIS IS FOR TESTING PURPOSES ONLY.
instructions: Please enter your full postcode, including both the outward-code and inward-code. For example, 'SW1A 0AA'.
type: text
datatype: ukpostcode

Partial UK postcode

In the example below, we demonstrate how to capture a portion of the UK postcode without having to use datatype: ukpostcode.

QPOSTCODE only requires the out-code and first digit of the in-code for the respondent. The validation makes sure it follows the proper format. Responses can then be matched to UK postcode spreadsheets for demographic purposes.

POSTCODE. What is your postcode? Please enter the first part, and then the first digit in the second part of your home postcode?
instructions: For example if your full postcode is "AB12 3CD" please enter "AB12 3" including a space. This is to assess the geographic region you live in more accurately. It will only be used to help analyse the results of this survey.
type: text
size: 5
maxlen: 6
cvalue: {uc $QPOSTCODE}
validation: [value] =~ /^[A-Z]{1,2}\d[A-Z\d]?\s\d$/ {message: Please enter the first part of your postcode. For example if your full postcode is "AB12 3CD" please enter "AB12 3" including a space.}
dta: 99. Prefer not to say