Repository navigation
CSDL member properties grouped by their level - #186
Merged
Merged
Conversation
A member property is a value of each member of its level, not a column
of its own: the education of each customer. Its CSDL property now names
the level property in bi:GroupBy, so a client groups its values by their
members as well. Power BI then adds the level, hidden, to its queries:
VALUES('Customers'[Customers.Customers.Name.Education]) becomes
SUMMARIZE(VALUES('Customers'), 'Customers'[Customers.Customers.Name],
'Customers'[Customers.Customers.Name.Education]). The measures are
computed of each member, a distinct count as Customer Count no more
aggregates the members of a value, which failed over more of them than
maxConstraints.
Signed-off-by: dbulahov <bulahovdenis@gmail.com>
stbischof
approved these changes
Nov 2, 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.
What does this PR do?
A member property is a value of each member of its level, not a column of its own: the education of each customer. Its CSDL property now names the level property in bi:GroupBy, so a client groups its values by their members as well. Power BI then adds the level, hidden, to its queries: VALUES('Customers'[Customers.Customers.Name.Education]) becomes SUMMARIZE(VALUES('Customers'), 'Customers'[Customers.Customers.Name], 'Customers'[Customers.Customers.Name.Education]). The measures are computed of each member, a distinct count as Customer Count no more aggregates the members of a value, which failed over more of them than maxConstraints.