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
Improve Relationship UI Wording to Better Reflect Filter Propagation Direction
The current relationship dialog can be confusing because the UI labels "From" and "To" do not always align with users' linguistic expectations regarding filter propagation. As per document : Relation...v-varunvv50 seconds agoMicrosoft EmployeeNew0Views0likes0CommentsDynamic 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 minutes agoNew MemberNew222Views2likes1CommentTenant and/or App/Workspace Banner messages- alerts
As a tenant admin - would like to publish banner messages or alerts as needed for the organization in the event of a data load failure, or other messaging that needs to be show to the end user on l...sue_yerly40 minutes agoNew MemberNew378Views18likes3CommentsSlicer option to show no data when no value is selected
Hello Power BI Team, Description: Currently, when the "Select All" option is enabled in a slicer, selecting it displays all related values as expected. However, when "Select All" is de-selected and...7407543 hours agoNew MemberNew3Views0likes0CommentsParameterize Dataflow Gen2 data source connection
Allow the Dataflow Gen2 data source connection GUID to be parameterized and stored in a Variable Library. This would allow the same Dataflow to use different connections depending on the workspace/e...frithjof_v5 hours agoCommunity ChampionNew16Views1like0Comments