« How to Use Objects - Calling "Methods"   |   Available Methods »

Methods for Specifying Objects

Designer Administrator
This manual is in pilot operation.
When expression examples are shown in this section, unless otherwise noted, the examples use dialects other than the Member Criteria Expression. Because the objects specified by objects specified by Label constants differ between the Member Criteria Expression and other dialects, expressions that look the same may be interpreted differently.

There are four methods to specify objects.

1. Using Predefined Identifiers

The predefined identifiers are Dimensions, Ledgers and Editions.

Dimensions represents a Dimension Group object. A Dimension Group object has no notable functions and is used as a starting point to retrieve individual Dimension objects.

  Dimensions!#ACCOUNT (1)
1 Specifies the Accounts Dimension object. (For the ! symbol, see “Methods for specifying child objects of already specified objects”.)

Ledgers represents a Ledger Group object. A Ledger Group object is used to determine the Ledger associated with a cell to which a text expression is applied.

  Ledgers!@CUR.Label (1)
1 Represents the label of the “current” Ledger (that is, the Ledger associated with the cell to which the text expression is applied). (For the ! symbol and @ functions, see “Methods for specifying child objects of already specified objects”.)

Editions represents a Ledger Edition Group object. A Ledger Edition Group object is used to obtain information such as the key of the currently accessed Ledger Edition.

  Editions!@CUR.Key (1)
1 Represents the Ledger Edition Key of the “current” Ledger Edition (that is, the Ledger Edition currently being accessed). (For the ! symbol and @ functions, see “Methods for specifying child objects of already specified objects”.)

2. Using Label Constants

You can specify objects by describing labels in expressions. The type of object specified by a label depends on the expression dialect. Specifically, in dialects other than the Member Criteria Expression and Field Value Derivation Expression, a Dimension object is specified. In the Member Criteria Expression, a Property object is specified and in the Field Value Derivation Expression, a Field object is specified.

  • General dialects (that is, dialects other than the Member Criteria Expression and Field Value Derivation Expression)

  #ACCOUNT
    => Specifies the “Accounts” Dimension object.

  • Member Criteria Expression

  #LEAF
    => Specifies the “Is Leaf” Property object of the member under inspection.

  • Field Value Derivation Expression

  YEAR
    => Specifies the Field object labeled “YEAR”.

3. Specifying Child Objects of Already Specified Objects

Starting from an object specified by methods 1 or 2 above, you can specify its “child” objects. The child objects of each object are as follows.

Object Child Objects of the Object on the Left

Dimension Group

Dimensions

Dimension

Members

Member

Property Values

Ledger Group

Ledgers

Others

(None)

To specify a child object, append the label or an @ function of the child object to the expression that specifies the parent object, separated by !.

  • Using labels

  #ACCOUNT!PL1010
    => Specifies the Member object for the member that belongs to the “Accounts” Dimension and has the label _"PL1010"_.

  • Using @ functions

  #ACCOUNT!@CUR
    => Specifies the Member object for the “current member” of the “Accounts” Dimension.

@ functions can be applied only to Dimension Group, Ledger Group and Ledger Edition Group objects. The available functions are @CUR, @POV and @RKEY.

Applicable @ Functions for Dimension Group Objects

Function Specified Member

@CUR

Returns an object that is valid only in the Member Criteria Expression within a Member List Definition. The returned object is the “current Dimension”, that is, the Dimension to which the Member List Definition is applied.

CUR: Current

Applicable @ Functions for Dimension Objects

Function Specified Member

@CUR

Current Member
CUR: Current

@POV

Point-of-View Member
POV: Point of View

@RKEY

Responsibility Key Member
RKEY: Responsibility Key

⚠ For details of the “Current Member” and the “Point-of-View Member”, see Member Variables.

Applicable @ Functions for Ledger Group Objects

Function Specified Member

@CUR

Current Ledger (that is, the Ledger associated with the cell to which the text expression is applied)
CUR: Current

Applicable @ Functions for Ledger Edition Group Objects

Function Specified Member

@CUR

Current Ledger Edition
CUR: Current

You can also specify child objects across multiple levels.

  Dimensions!#ACCOUNT!@CUR!#LEAF (1)
1 Specifies the “Is Leaf” Property object of the “current member” of the “Accounts” Dimension. 
  Dimensions!@CUR!@CUR!#LEAF (1)
1 When written in a Member Criteria Expression within a Member List Definition, this specifies the “Is Leaf” Property object of the “current member” of the current Dimension.

4. Using Cell Range Specifiers

To specify a “Cell Range” object on a Form, use a Cell Range Specifier. There are two types of Cell Range Specifiers: binary form and unary form. Cell Range Specifiers can be used only in some expression dialects on Forms. For details, see List of text expression dialects.

  • Binary form

      [SALES, TOTAL]
    => Indicates the cell range at the intersection of the “Sales” column and the “Total” row (assuming SALES is the column label for “Sales” and TOTAL is the row label for “Total”).

  • Unary form

    • When the text expression is used as a calculation expression for a Form “Column Spec.”

        [SALES]
    => Indicates the cell range at the intersection of the row where the expression is evaluated and the “Sales” column.

    • When the text expression is used as a calculation expression for a Form “Row Spec.”

        [TOTAL]
    => Indicates the cell range at the intersection of the column where the expression is evaluated and the “Total” row.

  • Relative references (fusion_place >= 14.1)

    Cell Range Specifiers can specify integer values in addition to labels. When numeric values are specified, they indicate relative positions from the current cell. By using relative references, you can create flexible expressions such as assigning sequential numbers or changing calculation methods based on referenced values. If there is no column or row at the specified position, no error occurs and 0 is returned.

      [-2,3]
    => Refers to the cell located two columns to the left and three rows below the current cell.

    As with label-based references, they can also be used as calculation expressions for Row Specs or Column Specs.

      IF [-1,WEEKDAY].Value = "SUN" THEN
  	[-1,0]
  ELSE
  	[-1,0]+1
  ENDIF
    => Depending on the value of the referenced cell, either displays the value of the cell immediately to the left of the current cell as is or displays the value incremented by 1.
      [-1]+3
    => When used as a calculation expression for a Row Spec., displays the value obtained by adding 3 to the value of the cell immediately to the left of the current cell. In this case, the values in the row are displayed as “0, 3, 6, 9...”.

    You can also specify a combination of labels and numeric values.

      [SALES,3]
    => Refers to the cell located three rows below the current cell in the SALES (Sales) column.

    If numeric values are omitted, they are treated the same as 0. That is, [,] has the same meaning as [0, 0].

      [,] >=100
    => When `[,]` is used in a validation rule of a Cell Spec., it refers to the value of the current cell. In this example, the rule is valid when a value of 100 or greater is entered.
    When specifying non-zero integers in relative references, note that the circular reference check in Form settings is not performed.

  • Column and row references with loop scopes (fusion_place >= 14.1)

    When you want to reference columns or rows within the loop that contains the source cell, you can specify a loop scope. By using a loop scope, you can reference and aggregate all columns or rows generated within the specified loop.

    In the example below, the total of columns or rows labeled DAILY within the loop of the #PERIOD (Relative Period) Dimension is obtained. For example, if there are three loop details in the Relative Period loop, three columns or rows labeled DAILY are generated and the total of the three is obtained.

      [#PERIOD::DAILY,LABEL2].total(
    [#PERIOD::DAILY,LABEL3],5)

    When aggregating by referencing specific columns or rows from outside the loop, you can specify them without a loop scope (for example, #PERIOD) such as [DAILY].total.

    On the other hand, when using the conditional aggregation methods, if you want to use multiple columns or rows of the same type (generated from the same Row Spec. or Column Spec.) as aggregation ranges or condition ranges, you must specify a loop scope.

    • Difference in reference ranges by colon specification

      As shown in the examples below, the reference range differs depending on whether one colon or two colons are specified.

      When two colons (::) are specified, all columns or rows labeled DAILY in all loop details within the #PERIOD loop are referenced. When one colon (:) is specified, only the columns or rows labeled DAILY within the loop detail that contains the source column or row in the same #PERIOD loop are referenced. See Image of loop scopes.

        #PERIOD:DAILY
  #PERIOD::DAILY

Image of Loop Scopes (fusion_place >= 14.1)

For example, in a loop specified by the Accounts (#ACCOUNT) Dimension, the details for each account are called loop details. Within each loop detail, columns or rows defined by Row Specs or Column Specs inside the loop specification are generated. In the example below, Budget rows and Actual rows are generated within each loop detail.

  Loop            Example: P/L account loop of the Accounts (#ACCOUNT) Dimension
    Loop Detail     Example: Revenue loop detail in the P/L account loop
      Row             Example: Budget row in the Revenue loop detail / BUDGET
      Row             Example: Actual row in the Revenue loop detail / ACTUAL
    Loop Detail     Example: Cost of Sales loop detail in the P/L account loop
      Row             Example: Budget row in the Cost of Sales loop detail / BUDGET
      Row             Example: Actual row in the Cost of Sales loop detail / ACTUAL
    (And so on)

In the example above, when #ACCOUNT:BUDGET is referenced from the ACTUAL row in the Revenue loop detail, the BUDGET row that belongs to the Revenue loop detail is referenced.

On the other hand, when #ACCOUNT::BUDGET is referenced, BUDGET rows in other loop details such as Cost of Sales are also included in the reference.