User-context calculated columns
A user-context calculated column is a calculated column that's evaluated per user. Its expression can call functions such as USERPRINCIPALNAME or USERNAME and return a different value for each user. In contrast, a standard calculated column is evaluated once, when the table is processed, and returns the same value for all users.
The calculated column's ExpressionContext property sets whether the column is evaluated once or per user:
| Expression Context | Meaning |
|---|---|
| Standard | The default. The expression can use only standard functions. The column has one value per row for all users. |
| User Context | The expression can call user-context functions. The column is evaluated per user. |
Select a calculated column in the TOM Explorer view and set Expression Context under Options in the Properties view.
Note
ExpressionContext requires compatibility level 1705 or higher, and below 1705 calculated columns are always Standard.
What a user-context column can't be used for
Objects evaluated once for the whole model can't reference a user-context calculated column. The Tabular Editor Semantic Analyzer reports an error for each of these cases:
| A user-context column can't be referenced by | Message |
|---|---|
| A standard calculated column | "This expression references the user-context-aware calculated column Table[Column], which is not allowed in a standard calculated column." |
| A calculated table | "This expression references the user-context-aware calculated column Table[Column], which is not allowed in a calculated table." |
| A row-level security filter | "This expression references the user-context-aware calculated column Table[Column], which is not allowed in a row-level security filter." |
| A relationship, as an endpoint | "A relationship cannot use the user-context-aware calculated column Table[Column] as an endpoint." |
The first three rules also apply to indirect references, for example through a measure. Measures and other user-context calculated columns can reference a user-context column.
Where the errors appear
| How the column is referenced | DAX editor | Messages view | te validate |
|---|---|---|---|
| Directly | Yes | Yes | Yes |
| Indirectly, for example through a measure | No | Yes | Yes |
| As a relationship endpoint | No | Yes | Yes |
The DAX editor doesn't underline indirect violations, so check the Messages view for them before you deploy.
A relationship-endpoint violation also appears in the relationship's Error Message property. Active and inactive relationships are both checked, with errors reported per endpoint, so a relationship with user-context columns on both sides has two.
Note
te validate --errors-only still reports these violations, because the option hides only warnings and anti-patterns.