Data field names and formats
This topic describes the data field names and formats supported by NLG Apps and Arria Answers.
For app-specific data requirements — such as minimum and maximum number of dimensions and measures — see the NLG Apps Directory.
Measures
Note
A measure* is a field containing measurable, quantitative values that can be used in calculations (e.g. Sales and Profit).
*The Arria visualization categorizes MicroStrategy metrics as measures.
There are no restrictions on field names for measures. The aggregation type and data format requirements are:
Measures must be numeric and have one of the following aggregation types: Sum, Average, Minimum, Maximum, or Count*.
Not all aggregation and entity type combinations are supported by every app. See the NLG Apps Directory for app-specific guidance.
Decimal separators must be periods; thousand separators, if used, must be commas.
*Arria Answers does not support measures aggregated by Count. See Query types for guidance on which aggregation types are required by each type of query.
Dimensions
Note
A dimension* is a field containing non-measurable, qualitative values (e.g. Country, Product, and Date). Dimensions can be used to categorize measures and provide context to your data.
A time dimension is a dimension field that contains whole date, year, quarter, month, or day values, only. Time dimensions can be used to perform analysis over time or to categorize your data.
A dimension instance is a unique value in a dimension field. For example, Scotland may be an instance of the Country dimension and February may be an instance of the Month time dimension.
*The Arria visualization categorizes MicroStrategy attributes as dimensions.
With the exception of time dimensions, there are no restrictions on the field names and data formats for dimensions.
The restrictions on time dimensions are described below. When data fields follow these conventions, Arria for MicroStrategy automatically recognizes them as time dimensions and changes their entity type to DateTime. You can also set the entity type manually in Step 2 of the wizard.
The following time dimensions are supported:
Supported field names
Date fields must be named as follows:
Naming Rule | Example Field Names |
|---|---|
*date* |
|
The asterisks (*) are wildcards that represent one or more characters, including letters, spaces, hyphens, and underscores. These rules are case-insensitive.
Tip
You can use the Alias field in the NLG Apps wizard and Arria Answers wizard to override field names.
Supported data formats
Date values must be in one of the following formats:
Pattern | Example Values |
|---|---|
|
|
|
|
|
|
|
|
If your Date field is not in a supported format, do the following:
In MicroStrategy, go to the Datasets panel.
Right-click your Date attribute, go to Data Type, and select the Date option from the dropdown field.
Click OK. A new date attribute is created (Date 1).
Right-click the new date attribute, go to Number Format, select Custom from the dropdown field, and enter
dd/mm/yyyy(or another supported format) in the last, blank field.
Click OK. Now use the new date attribute with the Arria for MicroStrategy visualization.
Supported field names
Year fields must be named as follows:
Naming Rule | Example Field Names |
|---|---|
y |
|
*yr* |
|
*year* |
|
The asterisks (*) are wildcards that represent one or more characters, including letters, spaces, hyphens, and underscores. These rules are case-insensitive.
Tip
You can use the Alias field in the NLG Apps wizard and Arria Answers wizard to override field names.
Note
The Arria visualization recognizes the MicroStrategy Date (Year) time attribute field as a year field.
Supported data formats
Year values must be a two-digit or four-digit number (e.g. 22 or 2022).
Supported field names
Quarter fields must be named as follows:
Naming Rule | Example Field Names |
|---|---|
q |
|
*qt* |
|
*qtr* |
|
*quarter* |
|
The asterisks (*) are wildcards that represent one or more characters, including letters, spaces, hyphens, and underscores. These rules are case-insensitive.
Tip
You can use the Alias field in the NLG Apps wizard and Arria Answers wizard to override field names.
Note
The Arria visualization recognizes the MicroStrategy Date (Quarter) time attribute field as a quarter field.
Supported data formats
Quarter values can be in alphanumeric or numeric form:
Quarter | Example Alphanumeric Values† | Example Numeric Values |
|---|---|---|
Quarter 1 |
|
|
Quarter 2 |
|
|
Quarter 3 |
|
|
Quarter 4 |
|
|
† Any combination of the strings Q, Qt, Qtr, and Quarter followed by a number — with or without spaces — is acceptable, so Q4 and Q 4 are equally valid. Also, any mixture of cases is acceptable, so qtr1 and QTR1 are valid alternatives to Qtr1.
Supported field names
Month fields must be named as follows:
Naming Rule | Example Field Names |
|---|---|
m |
|
*mon* |
|
*mth* |
|
*month* |
|
The asterisks (*) are wildcards that represent one or more characters, including letters, spaces, hyphens, and underscores. These rules are case-insensitive.
Tip
You can use the Alias field in the NLG Apps wizard and Arria Answers wizard to override field names.
Note
The Arria visualization recognizes the MicroStrategy Date (Month) time attribute field as a month field.
Supported data formats
Month values can be in text or numeric form:
Month | Example Text Values† | Example Numeric Values |
|---|---|---|
January |
|
|
February |
|
|
March |
|
|
April |
|
|
May |
|
|
June |
|
|
July |
|
|
August |
|
|
September |
|
|
October |
|
|
November |
|
|
December |
|
|
† This requirement is case-insensitive, so "JAN", "JAn" and "jan" are valid alternatives to "Jan".
Supported field names
Day fields must be named as follows:
Naming Rule | Example Values |
|---|---|
d |
|
*day* |
|
The asterisks (*) are wildcards that represent one or more characters, including letters, spaces, hyphens, and underscores. These rules are case-insensitive.
Tip
You can use the Alias field in the NLG Apps wizard and Arria Answers wizard to override field names.
Supported data formats
Day values must be a one-digit or two-digit number (e.g. 5 or 05). Ordinal numbers (e.g. 5th) are not supported.
