Dimensions are comprised of hierarchies. Hierarchies are comprised of members.
Import a new hierarchy
To import a new hierarchy:
- Select Import.
- Select Append or Replace.
| Value | Result |
| Append | This option appends the specified members to the existing hierarchy. |
| Replace | This option removes all current members in the hierarchy and replaces them with the members listed in the hierarchy import file. This option is typically used when setting up a new tenant. Otherwise, this option is to be used with caution. If data has been loaded to the tenant, the data may need to be reloaded after the Hierarchy Import. |
- Select the file to import from the dialog.
- Select Import to import the file.
File format for a hierarchy import
The import file can be an Excel or comma-delimited file. The first row must be a header row with the column name for the dimension table. Mandatory columns are:
| Column Header | Description |
| Name | Displays name of the member. Valid characters for member names are limited to letters, numbers, underscores, parentheses, and spaces:
|
| ParentName | Displays the name of the parent member. Null for root members. |
| IsLeaf | Specifies whether this is a leaf member. Valid values:
|
| Caption | Displays name of the caption for the member. Can be left blank. |
Member names with leading zeroes aren't supported, for example, 0001.
Optionally, a column can be included for attributes. The column name naming convention is p_attributename, where attributename is the name of the attribute.
For example:

Validation
The import file is validated for consistency. The file must meet these criteria:
- The member's name must be distinctive in the dimension.
- The parent's name can't be set to a leaf.
Export hierarchies
To export the dimension to an output file:
- Select Export from the toolbar.
- Select the File Format: Excel or CSV.
- Select the Export Keys checkbox to export the key value instead of the name.
Usually, you can export without keys unless there's a very specific reason that you require keys. - The file is exported to the Downloads folder. The naming convention of the file name is the name of the dimension exported.
Import and export alternate hierarchies
Additionally, the Hierarchy Manager supports importing and exporting alternate hierarchies. The key points to keep in mind when importing and exporting alternate hierarchies:
- You can export and import using the export and import icons in the toolbar when in Alternate Hierarchy mode.
- The import and export files don't include keys and don't support importing and exporting with keys.
- When you import, the action changes all the members in the alternate hierarchy to those in the hierarchy file. There isn't an Append option for this feature.
- Properties of leaf members aren't imported: Properties of leaf members in an alternate hierarchy are inherited from those in the default hierarchy. Translations for leaf members are also inherited from the default hierarchy.
- For leaf members: Tags and Operators (for Account members) can be uploaded via the hierarchy import file.
- For parent members: Names, Tags, Captions (including translated captions), and Operators (for Account members) can be uploaded via the hierarchy import file. You can also add translations to parent nodes in an alternate hierarchy using the Member Editor.
Note: Shared members aren't supported in Alternate Hierarchies. A message is returned if the Hierarchy Import file includes shared members.