DAX Base Measure

Modified on Sun, 26 Jul at 4:31 AM

Overview

.Base Measures begin with a period and provide the default calculations for raw measurable fields in a QQube FACT table.

They contain no date or business filters. Most are simple SUM calculations, while rate measures use a dynamic division of amount by quantity.

Measurable FACT Field Categories

Field CategoryDefault MethodPurpose
CountSUMContains an integer value of 1 for each line. Count fields can also appear in some dimensions.
AmountSUMProvides the total monetary value for the current filter context.
QuantitySUMProvides the total quantity for the current filter context.
Line RateDIVIDECalculates a dynamically accurate rate by dividing an amount measure by a quantity measure.
Line Exchange RateDIVIDECalculates an exchange rate dynamically rather than averaging stored line values.

Why Rates Do Not Use AVERAGE

A simple average of Line Rate or Line Exchange Rate does not produce an accurate result when quantities or amounts differ by line. QQube therefore divides the applicable amount measure by the applicable quantity measure.

Base Measure Examples

Summed Amount

.Line Sales Amount = SUM ( 'SALES VALUES'[Line Sales Amount] )

Dynamically Calculated Rate

.Line Rate = DIVIDE ( SUMX ( 'SALES VALUES', 'SALES VALUES'[.Line Sales Amount] ), 'SALES VALUES'[.Line Sales Quantity] )

Usage

.Base Measures contain no filters. They return the complete FACT-table value for the current report context by using either a raw SUM or a dynamic DIVIDE calculation.

When to Use a .Base Measure

Use a .Base Measure whenever the calculation must include the complete FACT-table value. Other QQube measures may stop at the Today Date defined in the QQube Configuration Tool.

Flexible Period Financial Statement Variations

Flexible Period financial statement data models contain two .Base Measure categories:

CategoryPurpose
.Base MeasuresProvides calculations for users who do not want to use the QQube account hierarchies.
.Base Measures For HierarchiesUses QQube account dimensions and supporting hierarchy measures to handle ragged financial-statement hierarchies.

QQube supplies specialized account dimensions for financial statements with uneven account depths. Measures in .Base Measures For Hierarchies use those dimensions to return the appropriate value at each visible hierarchy level.

Standard Financial Base Measure

.Actual = SUM ( 'PROFIT AND LOSS MEASURES'[Actual Amount] ) * MAX ( 'Account'[Sign to Apply] )

Hierarchy-Aware Financial Base Measure

.Hierarchy Actual = VAR ProfitAndLossActual = SUM ( 'PROFIT AND LOSS MEASURES'[Actual Amount] ) * MAX ( 'Account'[Sign To Apply] ) RETURN VAR AccountBrowseDepth = [[DAXP]] AccountBrowseDepth] VAR AccountRowDepth = [[DAXP]] AccountRowDepth] VAR _IsLeaf = IF ( HASONEVALUE ( Account[Account Has Children] ), VALUES ( Account[Account Has Children] ) ) VAR Result = SWITCH ( TRUE (), AccountBrowseDepth = AccountRowDepth + 1 && NOT ( ISBLANK ( ProfitAndLossActual ) ) && _IsLeaf = TRUE (), ProfitAndLossActual, AccountBrowseDepth <= AccountRowDepth, ProfitAndLossActual ) RETURN Result

Hierarchy Measure Behavior

The hierarchy-aware measure evaluates the visible account depth, row depth, and leaf status before returning the signed financial value. This prevents ragged account structures from displaying values at inappropriate hierarchy levels.

Expected Result

.Base Measures provide reusable, unfiltered calculations for raw QQube FACT fields. Standard measures return summed or dynamically divided values, while hierarchy-aware variations handle the uneven account structures found in Flexible Period financial statements.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article