Cube Configuration

Flow Member Properties

This guide covers the member-level properties for the Flow dimension — the settings that control sign behavior, type switching for translation, alternate input currency processing, and flow hierarchy design. Flow members also support the common properties shared by all dimension types (identifiers, descriptions, security, display order) and the same FormulaType, AllowInput, and IsConsolidated properties as Account members — see Account Member Properties for those shared definitions. For UD member properties (defaults, attribute members, RelatedDimensionType), see UD Member Properties. For how dimensions are created, named, and assigned to cubes, see Dimension Library and Inheritance.

Flow Dimension Member Properties

Flow members are configured at Application > Cube > Dimensions > Flow Dimensions. Select a flow member and open the Member Properties tab.

SwitchSign

ValueBehavior
TrueFlips the debit/credit sign of data for this flow member
FalseKeeps the sign as-is (default)
Use case: Contra accounts and flow activity members where users enter positive values but the amount should decrease the total. For example, a "Disposals" flow member on an asset account — users enter the disposal amount as positive, and SwitchSign reverses it during aggregation so it reduces the asset balance.

SwitchType

ValueBehavior
TrueSwitches the AccountType behavior — for example, treats an Asset as an Expense for translation purposes
FalseKeeps the original AccountType behavior (default)
Primary use case: Balance sheet rollforward activity members. When an Asset account has activity flow members (Additions, Disposals, Depreciation), those activity members represent periodic changes — they behave like income statement items for translation purposes. Setting SwitchType = True on these flow members causes the engine to translate the activity amounts at the average rate (like an Expense) rather than the closing rate (like an Asset).
⚠️Warning
NonFinancial accounts are not impacted by SwitchType. If you need SwitchType behavior on a non-monetary account, you must use a financial AccountType (Revenue, Expense, Asset, or Liability) instead.

FormulaType, AllowInput, IsConsolidated

Flow members support the same FormulaType, AllowInput, and IsConsolidated properties as Account members. The behavior is identical — see Account Member Properties for details.

FlowProcessingType

FlowProcessingType defines alternate input currency behavior on the flow member. To use these settings, the account's UseAlternateInputCurrencyInFlow property must be True (except for IsAlternateInputCurrencyForAllAccounts).
FlowProcessingTypeDescription
(None)Default. No alternate currency processing.
IsAlternateInputCurrencyThe flow member holds an override value in the currency specified by the AlternateInputCurrency property. Requires the account's UseAlternateInputCurrencyInFlow = True.
IsAlternateInputCurrencyForAllAccountsOpens currency overrides for all accounts, regardless of the account-level UseAlternateInputCurrencyInFlow setting.
TranslateUsingAlternateInputCurrency, InputLocalOverrides the translated value with the amount input at the local currency level. Activates the SourceMemberForAlternateInputCurrency property.
TranslateUsingAlternateInputCurrency, DeriveLocalOverrides the translated value and derives the local currency value based on the local currency rate. Activates the SourceMemberForAlternateInputCurrency property.
⚠️Warning
Alternate input currency processing only works at the base entity level — it does not flow through consolidation. This feature is well-suited to smaller applications where reducing the number of Business Rules is a priority. For larger or multi-level consolidation scenarios, handle currency overrides in Finance Business Rules instead.
Related Flow properties:
  • AlternateInputCurrency — The currency for the source value override (e.g., USD, EUR). Typically matches the application's default currency.
  • SourceMemberForAlternateInputCurrency — The specific flow member whose value is used as the override source for the current flow member.

Flow Hierarchy Design

A well-designed Flow dimension serves two purposes: providing a basis for cash flow reporting and giving a currency translation proof by showing calculated FX amounts for every balance sheet line item.
Simple vs. Complex Flow:
  • A simple flow hierarchy has minimal members — Ending, Periodic, and a few activity members. Suitable for applications without detailed rollforward requirements.
  • A complex flow hierarchy breaks out detailed activity types — Additions, Disposals, Depreciation, Reclassifications, FX Impact — giving full visibility into balance sheet movements. The MarketPlace provides both Standard and Complex Flow dimensions as starting points.
Cash Flow in Flow vs. Account:
  • Modeling cash flow in the Flow dimension provides a natural rollforward structure — each flow member represents a type of movement.
  • Modeling cash flow in the Account dimension treats each cash flow category as a separate account with its own hierarchy. This approach is simpler when cash flow reporting does not need to align with balance sheet rollforward.

Related Content