Detail of Member Properties

Designer
This manual is in pilot operation.

This section explains the prerequisite knowledge necessary for designing member properties.

Related Documents: Member Properties

Usage of Member Properties

Properties can be used to write conditional expressions when filtering target members. Specifically, conditional expressions based on property values can be written for the definitions of the following system objects:

  • "Member List" expression in "Dimensions"

  • "Member List" expression in "Loop Specification" and "Parameter Specifications" of "Forms"

  • "User-defined Mask Conditions" in "Ledger Masks"

  • "Read Permission Expression" and "Write Permission Expression" in "Access Permission Types"

User-defined Properties and Built-in Properties

Designers can decide and add properties for each dimension as needed. For example, setting up a "Manufacturing/Sales/Administration Classification" for the Department Dimension, or an "Account Classification" for the Account Dimension. Properties registered by designers in this way are called "User-defined Properties".

On the other hand, there are some properties that are common to all dimensions pre-determined. Also, virtual dimensions and built-in dimensions have their unique properties. These two types of properties are called "Built-in Properties". In addition to being used for specifying member selection conditions, built-in properties also have their unique roles.

⚠ The values of member properties are enumeration types. That is, multiple choices are prepared for each property, and one of them is selected and specified for each member. Choices are usually registered for each property as "Value definitions".

Data Type of Properties

For user-defined properties, one of the following "Data Types" must be specified:

Enumeration

Allows setting values only included in the "Value definitions" list, which are pre-registered.

String

Allows setting any label value as the property value.

In the case of String type, "Value definitions" list is not necessary but can be registered. If registered, when changing the property’s data type from String to Enumeration, if the property value of each member matches a label in the "Value definitions" list, that definition will be inherited as the new property value. Conversely, if it does not match, the property value will be blank.