Configuring Studio usage and display of attributes

You can define properties Studio can use to determine how to display and process attributes.

For example, some numeric data falls withing a range of possible values and can effectively be displayed in a range filter. Other numeric data, however, is not meaningful within a range and should be displayed as a list of values.

To configure the usage and display of physical attribute data, use the following values:

Table 1. Usage and display properties for physical attributes and pre-defined metrics
Property Description
system-eid_approxCardinality Valid values include:
  • high

    The value is a range and should be displayed using a range filter

  • low

    The value is not a range, and should be displayed as a list of values.

  • not applicable

    Neither a range nor a list of values is an appropriate display of the data. Usually affects data such as geocodes that is neither a range nor a list, and is processed in some other way.

Use the Configuration Web Service to populate these metadata properties.

To configure the usage and display of attributes and predefined metrics defined in a view definition, use the following metadata properties:

Table 2. Usage and display properties for logical attributes and pre-defined metrics
Property Description
approxCardinality Valid values include:
  • high

    The value is a range and should be displayed using a range filter

  • low

    The value is not a range, and should be displayed as a list of values.

  • not applicable

    Neither a range nor a list of values is an appropriate display of the data. Usually affects data such as geocodes that is neither a range nor a list, and is processed in some other way.

Use the Entity Configuration Web Service to populate these metadata properties.