Labels and Names

Designer Administrator
This manual is in pilot operation.

Labels

For Design Objects and Administration Objects, it is required to attach a "Label" for identification. A label is a generalization of codes used for identification, such as "Account Code" and "Product Code".

An application, which is one of the design objects, must have a unique label within the system. That is, within a single system, you cannot have multiple applications with the same label.

Each object contained in an application also requires a label.

Uniqueness of Labels

In many cases, an object’s label must be unique within the application, but the following are exceptions:

Object Scope of Label Uniqueness

Objects contained in a Dimension
(Members, Properties, Member Lists)

Unique within the Dimension

Property Value Definitions

Unique within the Property

Labels must be within 20 characters and can include the following types of characters:

  • Uppercase alphabetic characters[1]

  • Numerals

  • Symbols[2]

However, for custom dimension labels, special characters other than "`` (sharp)" and "`` (underscore)" are not allowed[3].

Furthermore, from version 11.0 onwards, except for Fiscal Years, Relative Periods, Scenarios, and Views, it is possible to register label conventions for Template Members for each dimension through Template Member Label Constraints.

Names

In addition to labels, applications, design objects, and administration objects are required to have a "Name" that is easy for users to understand. Names can be given in multiple languages. The length is up to 100 characters, regardless of whether they are full-width or half-width characters. There are some characters that cannot be used in names (such as some rare kanji used in personal names).