1. On-premises 5.2
  2. Guides
  3. Tours
  4. Concepts
    1. Aggregate filter
    2. Alias
    3. Apache Avro™
    4. Apache Kafka™
    5. Applied filter
    6. Base table
    7. Bookmark
    8. Business schema
    9. Business schema view
    10. Business schema view column
    11. Business schema view formula column
    12. Column
    13. Connector
    14. Dashboard filter
    15. Dashboard folder
    16. Dashboard runtime filter
    17. Data agent
    18. Data alert
    19. Data destination
    20. Date system variable
    21. Distinct filter
    22. Expression
    23. External data source
    24. External session variable
    25. Filter expression
    26. Filter expression session variable
    27. Filter option
    28. Formula column
    29. Formula expression
    30. Full load
    31. Global Variable
    32. Incorta Analyzer Table
    33. Incorta Analyzer Table column
    34. Incorta Analyzer Table formula column
    35. Incorta Analyzer View
    36. Incorta Analyzer View formula column
    37. Incorta SQL Table
    38. Incorta SQL View
    39. Individual filter
    40. Insight filter
    41. Internal query expression
    42. Internal session variable
    43. Join
    44. Join condition
    45. Join condition column
    46. Join filter
    47. Join filter column
    48. Level based measure
    49. Load filter
    50. Local data file
    51. Local data folder
    52. Materialized View
    53. Materialized View Column
    54. Materialized View Formula Column
    55. Measure filter
    56. Miscellaneous system variable
    57. Multi-Source table
    58. Physical schema
    59. Physical schema table
    60. Physical schema table column
    61. Physical schema table formula column
    62. Physical schema table runtime security filter
    63. Presentation variable
    64. Prompt
    65. Query system variable
    66. Runtime business view
    67. Runtime business view formula column
    68. Runtime security filter
    69. Session variable
    70. Shared Storage
    71. SQL Interface
    72. Upgrade Readiness
    73. Variable
    74. Visualization
  5. Tools
  6. References
  7. Integrations
  8. Data applications
  9. Releases

Concepts → Incorta Analyzer Table Column

About an Incorta Analyzer Table Column

An Incorta Analyzer table column exists in an Incorta Analyzer Table and is a reference to a physical schema table column or business schema view column.

Properties of an Incorta Analyzer table column

An Incorta Analyzer table column has configurable and static properties. The following are the properties of an Incorta Analyzer table column:

PropertyControlDescription
Show in AnalyzercheckboxSelect to show as a selectable column in the Data Panel
Nameread onlyThe column’s name; used in the fully qualified name of the column
Labelread onlyA user-friendly name. The label for an Incorta Analyzer table column is defined in the column properties of the Analyzer.
Typeread onlyThe data type of the column. The data type of a column in an Incorta Analyzer table is determined by the source column.
Functiondrop down listSelect the Incorta function of the column.
An Incorta Analyzer table cannot have a key column in releases before 5.2.11. However, starting with 5.2.11, you can specify key columns in Analyzer tables.
Encryptdrop down listSelect if the column is encrypted in shared storage. Incorta Analyzer tables do not support encrypted columns. You cannot set this property; it is always false.

Type property

As a referenced column, the type property of an Incorta Analyzer table column is an immutable property. If the type property of a physical schema table column is changed, it will affect the referenced column in the Incorta Analyzer table. If the type property is changed to a type that cannot be properly type casted, you may need to recreate the Incorta Analyzer table.

Function property

The function property of an Incorta Analyzer table column not only determines how the Loader Service stores data for the column, but also influences how tools such as the Analyzer assign a specific behavior to the column. Before 5.2.11, an Incorta Analyzer table column could only function as a measure or a dimension. If you used a column from your physical schema table that functioned as a key, the Incorta Analyzer table would convert the function of the column. The conversion is based on how you assign the column in the Analyzer when building the Incorta Analyzer table. Starting with 5.2.11, you can specify key columns in Analyzer tables.

When you create the Incorta Analyzer table, the function of the column is determined by the Analyzer tray you have added the column to (grouping dimension or measure).

Note

If you edit the Incorta Analyzer table and change the column function in the Analyzer, you will need to manually update the column function in the Table Editor.

Function: Dimension

A dimension categorizes, describes, or groups data. Examples of a dimension column are State, Year, or City. Dimension columns do not require unique values.

A dimension column has an associated behavior in the Analyzer. When a user double-clicks a dimension column in the Data panel, the Analyzer automatically adds the column to the Grouping Dimension tray in the Insight panel.

Function: Measure

A measure is a measurement of data. Examples of a measure column are Revenue, Quantity, and Cost.

A measure column has an associated behavior in the Analyzer. When a user double-clicks a measure column in the Data panel, the Analyzer automatically adds the column to the Measure tray in the Insight panel.

Function: Key

In releases before 5.2.11, an Incorta Analyzer table would not allow the function of an Incorta Analyzer table column or Incorta Analyzer table formula column to be a key. However, starting with 5.2.11, you can specify key columns for Incorta Analyzer and SQL tables. Adding, removing, or changing key columns does not require running a load job as derived tables are refreshed as part of schema update jobs. The derived table’s unique index is calculated and saved as a snapshot DDM file each time the key columns are updated or the schema or table is loaded.

Make sure that the column or columns that you designate as key maintain row uniqueness because no deduplication is performed for derived tables. If the selected key columns result in duplicate key values, the Engine returns the first matching value whenever a single value of the key columns is required.

Encryption property

An Incorta Analyzer table does not support encrypted columns. In previous releases, you could use the Table Editor to explicitly specify a column to be encrypted.

Additional Considerations

Business schema view references

When creating an Incorta Analyzer table, you are able to access the business schema as a data source for an Incorta Analyzer table. There are several cases you should be aware of when utilizing entities in the business schema view as a data source.

Load service timing

An Incorta Analyzer table is one of the last tables loaded during a schema load. As a result, if the Incorta Analyzer table is referencing a business schema view column that references an entity that loads at the same time or later than the Incorta Analyzer table, it will cause the load to fail or the Incorta Analyzer table to error when attempting to display values. As an example, an Incorta SQL table is also loaded at the end of a schema load. If the Incorta Analyzer table references a business schema view that references an Incorta SQL table the load will fail. The same issue will occur if the business schema view is referencing another Incorta Analyzer table.

Circular dependencies

A business schema view column can reference an Incorta Analyzer table. The same Incorta Analyzer table can reference the same business schema view column. These types of cyclical dependencies will cause errors and should be avoided.

Session variables referenced in business schema

The value of a session variable is calculated at runtime. If an Incorta Analyzer table references a business schema view column that is referencing a session variable, the value of the session variable in the Incorta Analyzer table will be calculated at load time. Avoid making this reference as the session variable’s value may change between a physical schema load.