...
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.