Developer Documentation Library > Scripting > mrScriptMetadata User’s Guide > mrScriptMetadata reference > Field definitions
 
Field definitions
Field type
Description
Defines an integer question, which is a question that requires a whole number response.
Defines a real question, which is a question that requires a numeric response that can contain decimals.
Defines an open-ended question, which is a question that requires verbatim text as the response.
Defines a question that requires a date, a time, or a date and time as the response.
Defines a boolean question, which is a question that requires a response of True or False.
Defines a categorical question, which is a question that has a limited number of categories that represent the possible answers. Categorical questions can be single response or multiple response.
Defines a list of categories (sometimes referred to as a defined list or a shared list) that can be reused.
Defines an information item.
Defines a loop (a set of questions that are to be asked more than once) in which the number of times the loop is to be repeated (and therefore the number of times that the set of questions in the loop are to be asked) is controlled by the categories in a category list. For example, the loop can be repeated once for each product in a product list.
Defines a loop in which the number of times the loop is to be repeated is controlled by a numeric range expression.
Defines a grid, which is an alternative way of defining a categorical loop with the grid and expand keywords specified.
Defines a group of categorical questions and categorical loops that share a category list.
Defines a group of questions for presentation or organizational purposes.
Defines a group of questions that will be shown together on a page.
Defines questions from which the responses/iterations are generated from external databases.
Long, Double, Text, Date, Boolean, and Categorical questions are sometimes known as simple questions to differentiate them from fields such as loops and blocks that typically consist of multiple questions. You might see that term used in topics throughout the UNICOM Intelligence Developer Documentation Library.
Common parameters
<axis>
You can define an axis expression to be used in and the Tables Option. For more information, see Axis expressions.
<usage-type>
You can define usage types for fields that need to be recognized by products as having a special usage. For more information, see Special usage types.
<helperfields>
You can define Helper variables that are used to store supplementary information for a field. For more information, see Helper variables.
nocasedata
Specifies that case data should not be stored for this field.
unversioned
Specifies that the field can be changed at any time, regardless of the lock status of the current version of the metadata. Only versioned fields can be included in the routing of a questionnaire, which means that all of the questions that will be used for collecting data must be versioned. Unversioned fields are typically used for coding variables, so that as new categories are created, they can be used when coding data collected using previous versions of the metadata.
See
mrScriptMetadata reference