Cube Configuration

Account Member Properties

This guide covers the common properties shared by all dimension types (identifiers, descriptions, security, and display order) and the member-level properties for the Account dimension — the settings that control how each account member behaves during calculations, translation, and aggregation. For Flow member properties (SwitchSign, SwitchType, FlowProcessingType), see Flow Member Properties. For UD member properties (defaults, attribute members, RelatedDimensionType), see UD Member Properties. For Entity member properties (Currency, IsICEntity, PercentConsolidation, etc.), see Entity Dimension Setup. For Scenario member properties (InputFrequency, DefaultView, Workflow settings, etc.), see Scenario Types and Cube Dimensions. For how dimensions are created, named, and assigned to cubes, see Dimension Library and Inheritance.

Common Properties Across All Dimension Types

Every dimension member — regardless of type — has a standard set of read-only identifiers and shared properties.

General

PropertyDescription
IdNumeric identity assigned by the application when the member is created. Cannot be changed.
NameThe member name. Must be unique within its dimension type across all dimensions.
AliasOptional alternate names (comma-delimited) for referencing the member in Member Filters, Cube Views, or Business Rules without renaming the original member.
DimensionTypeRead-only. Indicates whether this is an Account, Flow, UD1, etc.
MemberDimensionRead-only. The dimension instance this member belongs to.

Descriptions

PropertyDescription
DefaultDescriptionFree-text description of the member. Also known as the Report Alias.
FullDescriptionAdditional culture-specific description fields (if configured in the Application Server Configuration File).

Security

PropertyDescription
DisplayMemberGroupControls which security group can see this member in dimension lists. Affects member visibility only, not data access.

PositionWithinParent (Relationship-Level)

This is a Relationship Property, not a Member Property — it varies per parent-child relationship. It controls the display order of the member under its parent in dimension lists. Members are sorted by this value in ascending order.

Account Dimension Member Properties

Account members are configured at Application > Cube > Dimensions > Account Dimensions. Select an account member and open the Member Properties tab.

AccountType

AccountType is the most important property on an account member. It defines the time balance behavior, sign convention, and translation behavior of the account.
AccountTypeValueTime BalanceTranslates?Sign ConventionTypical Use
Group0Determined by childrenN/A (parent)N/AParent/rollup members only
Revenue1Flow (periodic/YTD)YesCredit (+)Income statement — revenue line items
Expense2Flow (periodic/YTD)YesDebit (+)Income statement — expense line items
Asset3Balance (point-in-time)YesDebit (+)Balance sheet — asset accounts
Liability4Balance (point-in-time)YesCredit (+)Balance sheet — liability and equity accounts
Flow5Flow (periodic/YTD)No—Non-translating flow-type values
Balance6Balance (point-in-time)No—Non-translating balance-type values (legacy)
BalanceRecurring7Balance (does not change)No—Opening balances that persist unchanged (legacy)
NonFinancial8—No—Headcount, square footage, and other non-monetary data
DynamicCalc9On-the-flyNo—Calculated ratios and metrics that are never stored
ℹ️Info
Equity accounts should set AccountType to Liability. OneStream does not have a dedicated Equity account type — Liability covers both liabilities and equity because they share the same credit-normal sign convention and balance-sheet time balance behavior.
⚠️Warning
NonFinancial accounts are not impacted by the Flow member's SwitchType property. If you need SwitchType behavior (e.g., treating a balance-sheet rollforward activity as an income statement item for translation), use a financial AccountType instead.
Revenue and Expense accounts behave as flow-type values — they have both periodic and YTD views. The engine applies the debit/credit sign convention automatically during aggregation, so users can enter data as positive amounts for both revenue and expense. Asset and Liability accounts behave as balance-type values — they represent a point-in-time balance and translate using the rate type configured on the cube or scenario.

FormulaType

FormulaType controls whether the member stores data directly, runs a stored calculation, or computes on the fly.
FormulaTypeBehaviorStored?When It Runs
NoFormulaDefault. The member accepts input and data loads directly.YesN/A — data is entered or loaded
MemberFormulaA stored calculation defined in the member's formula editor. Runs during the Calculate phase.YesCalculate (before Finance Business Rules fire for that account)
DynamicCalcCalculated on the fly whenever the cell is read. Never stored in the database.NoEvery time the cell is queried
💡Tip
DynamicCalc on an Account member requires that the AccountType also be set to DynamicCalc. Both properties must agree — if you set FormulaType = DynamicCalc but leave AccountType as Revenue, the engine will not calculate the member correctly.
When to use each:
  • NoFormula — Input accounts, data load targets, driver accounts
  • MemberFormula — Calculated line items where the formula is simple and does not need Business Rule context (e.g., GrossProfit = Revenue - COGS). The formula can vary by Scenario Type and Time.
  • DynamicCalc — Ratios, percentages, and informational metrics that should never consume storage. Use sparingly — DynamicCalc members add overhead every time they are read.

AllowInput

ValueBehavior
TrueThe member can receive input from data entry forms and data loads
FalseThe member is read-only in input forms. It removes the member as a possible mapping target in data integration, preventing data from erroneously being mapped to it.
Best practice: Set AllowInput = False on calculated accounts (MemberFormula and DynamicCalc) and on parent/rollup accounts. This prevents accidental data entry that would be overwritten by calculations.

IsConsolidated

Controls whether the member participates in consolidation processing.
ValueBehavior
Conditional (True if no FormulaType)Default. Accounts without a FormulaType are included in consolidation. Accounts with a FormulaType are consolidated only if IsConsolidated is explicitly True.
True (regardless of FormulaType)Always included in consolidation
FalseNever consolidated — data stays at the base entity level
💡Tip
Set IsConsolidated = False for driver accounts (FTE, rates, growth percentages) that have no meaning when aggregated across entities. This improves consolidation performance by skipping unnecessary processing.

IsICAccount (Intercompany)

Determines whether the account participates in intercompany elimination.
ValueBehavior
FalseDefault. Not an intercompany account.
Conditional (True if Entity not same as IC)The account is treated as IC when the IC dimension member is a different entity than the current entity. Prevents an entity from recording IC with itself. Most common setting for IC accounts.
TrueAlways treated as an intercompany account regardless of the IC partner.
For the full intercompany elimination workflow, see the IC Configuration section in the Entity Dimension Setup guide.

PlugAccount

Selects the account that receives any non-eliminating difference when intercompany elimination runs. If Entity A has an IC balance of $5,000 and Entity B has $5,100 for the same IC pair, the $100 difference posts to the plug account.
Multiple accounts can be reclassified to the same plug account.

UseAlternateInputCurrencyInFlow

When True, the account uses an alternate currency override defined on Flow members (via FlowProcessingType). This allows data to be entered in a currency other than the entity's local currency, with the Flow dimension holding both the override value and the local-currency equivalent.

Input/Adjustment View Overrides

These properties override the scenario-level input and no-data-zero view settings for this specific account:
PropertyDefaultOptions
InputViewForAdjustmentsUseScenarioSettingPeriodic, YTD
NoDataZeroViewForAdjustmentsUseScenarioSettingPeriodic, YTD
NoDataZeroViewForNonAdjustmentsUseScenarioSettingPeriodic, YTD
Use these overrides when a specific account needs different view behavior than the scenario default. For example, a balance-sheet account in a scenario defaulting to Periodic view might need YTD treatment for adjustments.

Account Aggregation Settings

The Aggregation section controls which dimensions the account participates in when rolling up to parent members.
PropertyDefaultDescription
UsedOnEntityDimensionTrueAccount participates in entity hierarchy aggregation
UsedOnConsolidationDimensionTrueAccount participates in consolidation dimension aggregation
EnableFlowAggregationTrueAccount participates in Flow dimension aggregation
EnableOriginAggregationTrueAccount participates in Origin dimension aggregation
EnableICAggregationTrueAccount participates in IC dimension aggregation
EnableUD1AggregationTrueAccount participates in UD1 dimension aggregation
EnableUD2AggregationTrueAccount participates in UD2 dimension aggregation
EnableUD3–UD8AggregationTrueAccount participates in UD3 through UD8 dimension aggregation
Set any toggle to False to prevent the account from aggregating in that dimension. Click the cell to toggle between True and False.
💡Tip
Set all aggregation toggles to False for informational and driver accounts (FTE, headcount, rates, percentages). These values are meaningless when summed across entities or departments — aggregating them produces misleading totals and wastes processing time.

AggregationWeight

A decimal value controlling what proportion of the member's data aggregates to its parent. The default is 1.0 (100%).
Set to 0 for shared members that should not double-count when they appear under multiple parents. For example, if an account exists in both a detail hierarchy and a summary hierarchy, set AggregationWeight = 0 on the shared relationship to prevent the value from being counted twice at the top of the hierarchy.

Account Constraints (VaryByCubeType)

Properties in the VaryByCubeType category restrict which dimension intersections are valid for a given account. Constraints can vary by cube type (Standard, Tax, Treasury, etc.), allowing the same account to have different rules in different cubes.

IC Constraints and MemberFilter

Define which intercompany members are valid for this account. Use the MemberFilter field to specify allowed IC members. Invalid intersections receive no aggregation and no input.

Flow Constraints

Restrict which Flow members are valid for this account. Accounts that do not participate in rollforward analysis can exclude activity flow members.

UD2–UD8 Constraints

Restrict which UD members are valid for this account per cube type. For example, a revenue account might be valid for all Product Line members (UD2) in a Standard cube but only for specific product categories in a Tax cube.
Invalid intersections — where a constraint excludes the combination — receive no aggregation and no input. The engine skips these intersections during calculation and consolidation, improving performance and preventing data entry errors.

Accessing Member Properties in Code

You can read dimension member properties programmatically in Business Rules:
1' Get AccountType for a member
2Dim acctType As AccountType = api.Account.GetAccountType(accountMemberId)
3
4' Get FormulaType for an account
5Dim formulaType As FormulaType = api.Account.GetFormulaType(accountMemberId)
6
7' Get the plug account for an IC account
8Dim plugAcctId As Integer = api.Account.GetPlugAccount(accountMemberId)
9
10' Check Flow SwitchSign and SwitchType
11Dim switchSign As Boolean = api.Flow.SwitchSign(flowMemberId)
12Dim switchType As Boolean = api.Flow.SwitchType(flowMemberId)
13
14' Get cell-level AccountType (accounts for SwitchType on current flow)
15Dim cellAcctType As AccountType = api.Data.GetDataCellEx( _
16  "A#Revenue:F#Activity").AccountType
The cell-level AccountType method combines the account's base AccountType with the flow member's SwitchSign and SwitchType settings to return the effective AccountType for the current intersection.

Related Content