Skip to content

Loading and Unloading Dimensions

Dimensions can be maintained from workflow operations by loading data. In addition, dimensional data can be flattened into tabular data and stored in tables. This is often useful for enriching reporting and analytics data.

Since dimensions represent hierarchical data structures, the load process must convey the relationships in the data. PlaidCloud supports two different data structures for loading dimensions:

  • Parent-Child - The data is organized vertically with a Parent column and Child column defining each parent of a child throughout the structure
  • Levels - The data is organized horizontally with each column representing a level in the hierarchy from left to right

In addition to structure, other dimension information can be included in the load process such as values, aliases, and properties.

A levels (flat) load takes a default consolidation, which every interim node the load creates receives, and can name a leaf column: when it does, that column decides which node carries the row’s aliases, properties and values; otherwise the last filled level is the leaf.

A parent-child load’s default consolidation type applies to any row whose own consolidation is blank or unrecognised, so it must be one of the valid types even when the table also names a consolidation column. The hierarchy a load targets must not share its name with a column the load maps: a column of that name is read as the hierarchy each row belongs to, so a load naming both is refused rather than following one reading and ignoring the other.

A load of aliases, properties or values checks every row’s member before writing anything. If any row names a member the dimension does not hold, the load fails and reports those names, and nothing from that load is stored. Load the structure first, or include the missing members in it, then load the attributes.

See the Workflow Step for Dimension Load for more information.

Exporting dimensions to tables supports two structural approaches:

  • Parent-Child - The data is organized vertically with a Parent column and Child column defining each parent of a child throughout the structure
  • Levels - The data is organized horizontally with each column representing a level in the hierarchy from left to right

Properties and values can also be included in the flattened tabular data.

See the Workflow Step for Dimension Export for more information.