TJ-9000
Advocate I
1 year agoStatus:
New
Dynamic/Maintainable Scoping for Calculation Group Logic on Measures
In large Power BI semantic models, it’s common to need calculation groups (such as for currency conversion or time intelligence) that apply only to some measures—typically those with certain characteristics. Currently, the only way to scope calculation group logic (e.g., using ISSELECTEDMEASURE) is to manually list every affected measure. This is difficult to maintain as models grow and evolve.
Problem: there is no dynamic way in DAX to group or reference measures for calculation group logic:
- You can’t reference all measures in a given display folder.
- You can’t filter by metadata or custom tags.
- You can’t check for the existence of a measure or flag at runtime (e.g., with a TRY or IFERROR pattern).
- You can’t use naming conventions or wildcards in ISSELECTEDMEASURE.
- There’s no way for report authors to “opt out” of calculation group logic for new measures without requesting a central model change.
Impact:
- Calculation group maintenance becomes tedious and error-prone.
- Large or decentralized teams cannot easily adapt calculation group logic to evolving reporting needs.
- There’s no flexible, self-service way to manage calculation group scope.
Ideas for Improvement:
- Allow ISSELECTEDMEASURE to reference measures by folder, tag, or attribute (e.g., ISSELECTEDMEASURE(IN FOLDER "Currency Measures") or ISSELECTEDMEASURE(HAS TAG "Currency")).
- Introduce a DAX function to check for the existence of a measure or flag at runtime (e.g., TRY([MyFlagMeasure])).
- Support wildcards or naming patterns in measure selection.
- Enable more dynamic or metadata-driven scoping of calculation group logic, including per-report overrides.
Current Workarounds:
- Manually maintain long lists in ISSELECTEDMEASURE.
- Use external tools to regenerate calculation group DAX based on model structure (not dynamic).
- None of these are as flexible or maintainable as dynamic grouping would be.
Request:
Please consider adding support for more dynamic, maintainable, and metadata-driven approaches to scoping calculation group logic to measures in Power BI.
No CommentsBe the first to comment
Recent ideas
Metadata-Driven Copy Job Control at Table and Column Level
We currently achieve metadata-driven table and column selection in Copy Data activities by using dynamic queries. This allows us to dynamically determine which tables and columns should be processed ...Motasim091 hour agoNew MemberNew3Views0likes0CommentsDynamic ForEach Parallel Batch Count Based on Runtime Capacity
We would like Microsoft Fabric Data Factory to support dynamic configuration of the ForEach activity's parallel batch count at runtime. Currently, the ForEach batchCount is effectively configured as...Motasim091 hour agoNew MemberNew3Views0likes0CommentsMake Workspace-Level Surge Protection Limit Visible to Workspace Users
Please make the applicable workspace-level surge protection limit visible in the workspace settings. Currently, when surge protection is applied by Capacity Admins, workspace users don't get visibil...frithjof_v4 hours agoCommunity ChampionNew24Views0likes0CommentsAllow Custom Recipient Settings for Gateway Expiry Notifications
Now, during the final 90 days before the gateway version end-of-support date, operations continue, but semantic model contacts users can receive warnings in email The warning message is: "The on-prem...YuanMao5 hours agoNew MemberNew8Views1like0Comments