INDEX

Applies to: Calculated column Calculated table Measure Visual calculation

Returns a row at an absolute position, specified by the position parameter, within the specified partition, sorted by the specified order. If the current partition can't be deduced to a single partition, multiple rows may be returned.

Syntax

INDEX(<position>[, <relation> or <axis>][, <orderBy>][, <blanks>][, <partitionBy>][, <matchBy>][, <reset>] )

Parameters

Return value

A row at an absolute position.

Remarks

Each partitionBy and matchBy column must have a corresponding outer value to help define the "current partition" on which to operate, with the following behavior:

• If there is exactly one corresponding outer column, its value is used.
• If there is no corresponding outer column:
  • INDEX will first determine all partitionBy and matchBy columns that have no corresponding outer column.
  • For every combination of existing values for these columns in INDEX’s parent context, INDEX is evaluated and a row is returned.
  • INDEX’s final output is a union of these rows.
• If there is more than one corresponding outer column, an error is returned.

If matchBy is present, INDEX will try to use matchBy and partitionBy columns to identify the row. If matchBy is not present and the columns specified within orderBy and partitionBy cannot uniquely identify every row in relation:

• INDEX will try to find the least number of additional columns required to uniquely identify every row.
• If such columns can be found, INDEX will automatically append these new columns to orderBy, and each partition is sorted using this new set of OrderBy columns.
• If such columns cannot be found, an error is returned.

An empty table is returned if:

• The corresponding outer value of a PartitionBy column does not exist within relation.
• The position value refers to a position that does not exist within the partition.

If INDEX is used within a calculated column defined on the same table as relation and orderBy is omitted, an error is returned.

reset can be used in visual calculations only, and cannot be used in combination with orderBy or partitionBy. If reset is present, axis can be specified but relation cannot.

If the value of reset is absolute (i.e., a positive integer, HIGHESTPARENT or a field reference) and the calculation is evaluated at or above the target level in the hierarchy, the calculation resets for each individual element. That is, the function is evaluated within a partition containing only that specific element.

Example 1 - calculated column

The following DAX query:

EVALUATE INDEX(1, ALL(DimDate[CalendarYear]))

Returns the following table:

Example 2 - calculated column

The following DAX query:

EVALUATE
SUMMARIZECOLUMNS (
    FactInternetSales[ProductKey],
    DimDate[MonthNumberOfYear],
    FILTER (
            VALUES(FactInternetSales[ProductKey]),
            [ProductKey] < 222
    ),
    "CurrentSales", SUM(FactInternetSales[SalesAmount]),
    "LastMonthSales",
    CALCULATE (
        SUM(FactInternetSales[SalesAmount]),
        INDEX(-1, ORDERBY(DimDate[MonthNumberOfYear]))
    )
)
ORDER BY [ProductKey], [MonthNumberOfYear]

Returns the following table:

Example 3 - visual calculation

The following visual calculation DAX queries:

SalesComparedToBeginningOfYear = [SalesAmount] - CALCULATE(SUM([SalesAmount]), INDEX(1, ROWS, HIGHESTPARENT))

SalesComparedToBeginningOfQuarter = [SalesAmount] - CALCULATE(SUM([SalesAmount]), INDEX(1, , -1))

Enhance a table so it contains, for each month:
- the total sales amount;
- the difference to the first month of the respective year;
- and the difference to the first month of the respective quarter.

The screenshot below shows the visual matrix and the first visual calculation expression:

Related content

OFFSET ORDERBY PARTITIONBY WINDOW RANK ROWNUMBER