Creating table components (axes and ordinates)

An empty table has three fields that reflect the orientations of the axes - X, Y, and Z. To create a valid table you must create at least two axes X and Y.

The axes and their respective ordinates (row, column, sheet) can be created by using domains, members, and hierarchies or hierarchy nodes, which are presented in the left side sub-panel of the section: Tables. They can be placed in the table by using the drag-and-drop function.

Open

For example, let’s drag the MET1 Profit and loss statement metric hierarchy and drop it onto X-axis. After doing so, a new pop-up window will appear asking “do you want to add hierarchy children?”. In this case, the hierarchy children are the child elements of the MET1 Profit and loss statement: md1 Revenues, md2 Cost of production, and md3 Profit (loss).

Note that for the table to be reportable it must have a metric defined on one of the axes and at least one table cell that is the intersection between one row and one column.

Open

After clicking “yes” you will be asked to enter a code for the ordinate that will be applied to all concepts displayed on the ordinate.

Having completed all these steps, we observe that one ordinate has been added.

Creating an axis on the Y-ordinate requires a few additional steps:

After dragging and dropping the chosen hierarchy to the table, select a dimension in the pop-up window.

Select Hierarchy restriction. If you choose Yes you will create a semi-open axis without hierarchy children. If you choose No you will create a closed axis and will be able to keep hierarchy children.

Now, just add a code and the Y-ordinate is ready. If you do not want to have the code on ordinate you can go to model design rules and disable this rule.

Table axes can have explicit ordinates for example separately labeled headers of rows/columns/sheets or these headers may be rendered as a drop-down list. In case of the latter the axis is created as hierarchy restriction and the available options are members of the referred hierarchy. Typical examples are list of countries or currencies which are impractical for explicit enumeration for table definition (due to large number of known in advance values) as well as data edition/review where only headers that contain data that should be displayed.

Axis and ordinate edition

All axes and ordinates by default have a label inherited from the hierarchy/hierarchy node. It can be edited in the edit window.

For this, choose the axis or ordinate, click the 3 dots next to the element and select Edit.

Optional key

"This key is optional" is an attribute available only for open or semi-open axis' keys. This attribute enables data architects to mark some of the keys are not mandatory to fill in for every row/column in the template.

This property is reflected in XBRL taxonomy table linkbase as includeUnreportedValue attribute or asOptionalKey (BOOLEAN) column in the mAxis table when the model is exported as a database.