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
Support QR codes in the barcode scanner in the Power BI app
I was surprised to find that the barcode scanner inside of a Power BI report in the mobile app only supports scanning barcodes, not QR codes. Our warehouse uses QR codes everywhere, so I cannot use t...Jaap_O_RFH1 hour agoNew MemberNew11Views0likes0CommentsAllow enabling Lakehouse Schemas on an existing Lakehouse
Right now Lakehouse Schemas can only be turned on when you first create a Lakehouse. If you already have one running in production and later decide you need schemas, there is no way to enabled them o...AlessioAndriulo1 hour agoAdvocate INew7Views0likes0CommentsAllow enabling Lakehouse Schemas on an existing Lakehouse, without recreating it
Today, Lakehouse Schemas can only be turned on when a Lakehouse is first created. There is no supported way to enable schema support on a Lakehouse that already exists — the only workaround is creati...AlessioAndriulo2 hours agoAdvocate INew26Views4likes0CommentsWorkspace Folder & Subfolder Inventory View for Power BI Reports and Apps
Problem: Many organisations use Power BI workspace folders and nested subfolders to organise reports by department, business area, project, or function. While this structure helps keep content organ...rijesh2 hours agoFrequent VisitorNew6Views1like0Comments