TJ-9000
1 year agoAdvocate I
Status:
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
Provide a Read-Only / Source-Safe Mode for Schema Shortcuts in Lakehouse
Schema Shortcuts provide a much better management experience than individual Table Shortcuts because they preserve the source schema structure and allow multiple tables to be onboarded at once. Howev...Junghyoen41 minutes agoMicrosoft EmployeeNew10Views4likes0CommentsAccess Variable Library in Semantic Models
Enable the Variable Library as a centralized location for storing all environment‑specific variables, allowing us to adjust them for promotion scenarios (e.g., from dev to prod) without relying on de...FreddyH11 hours agoAdvocate IINew920Views31likes2CommentsEnhance Fabric Pipeline Monitoring with Parent-Child Pipeline Lineage and Parameter Visibility
Currently, Microsoft Fabric Pipeline monitoring lacks several capabilities that are available in Azure Data Factory, making troubleshooting and operational support challenging in enterprise environme...dwramreddy12 hours agoRegular VisitorNew8Views0likes0CommentsDynamic ADLS-Gen2 path input for Spark Jobs Main definition file
I would like the ability to add a dynamic input box on a spark job definition's "Main Definition File" "ADLS-Gen2 path". this would be useful to set base and variable paths across all spark jobs...mfink_db16 hours agoNew MemberNew238Views2likes2CommentsReintroduce Tenant/Capacity Switch to Control "Users can create Plan items" Post-GA
During the Preview phase of Fabric Plan items, administrators had access to a dedicated tenant/capacity setting: "Users can create Plan items". With General Availability (GA), this granular administr...Sri-Surendra_Ku19 hours agoNew MemberNew106Views14likes1Comment