Repository navigation
Direct Lake on OneLake calculated columns: document UserContext expression context requirement - #440
Merged
Conversation
…n OneLake calculated columns Calculated columns on Direct Lake on OneLake tables must use ExpressionContext = UserContext (CL 1705+); Standard fails on save. Remove unsupported claim that these columns ignore report filters and slicers.
mlonsk
marked this pull request as ready for review
October 26, 2026 14:55
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://blue-island-085db6f03-440.westeurope.6.azurestaticapps.net |
1 similar comment
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://blue-island-085db6f03-440.westeurope.6.azurestaticapps.net |
jeroenterheerdt
approved these changes
Oct 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Calculated columns on Direct Lake on OneLake tables only support the
UserContextexpression context (preview, unmaterialized). New calculated columns default toStandard, and saving one on a Direct Lake table fails with "Default expression context cannot be used for calculated columns in Direct Lake tables". A customer hit this from Tabular Editor 3 and the docs did not explain it.Changes:
tutorials/direct-lake-guidance.md: new section "Calculated columns on Direct Lake on OneLake" with the requirement, the engine error, the compatibility level 1705 prerequisite and the steps to set Expression Context in the Properties view. Limitation bullet and Composite models paragraph now point to it.features/user-context-calculated-columns.md: new "Direct Lake on OneLake tables" section linking to the guidance. Expression Context values shown asStandard/UserContextto match the Properties view.features/Semantic-Model/semantic-model-types.md: footnote 5 updated.Sources: