When I create a quick measure (visual-level calculation), I need to reference a column from the data table as the base. However, when I try to create this calculation in a visual where I’m using a field parameter, the column name changes depending on the selected parameter field, and as a result, the visual-level calculation throws an error.
Is there any way to make this work?
3 Comments
- kleigh
Responsive Resident
There isn't a solution at the moment - it is on the roadmap : https://community.fabric.microsoft.com/t5/Desktop/Share-your-thoughts-on-visual-calculations-preview/m-p/4744947#M1415334 - Gepax
Advocate I
I found an alternative… Ideally, it would work natively with the field parameter, but this is what I managed to do. I manually created a field parameter: prm_M_Tipo_Combustivel = DATATABLE( "Tipo", STRING, { {"Diesel"}, {"Arla"} } ) After that, I created a measure that uses “Measure A” if “Diesel” is selected, or “Measure B” if “Arla” is selected. I used this measure in the visual, created a moving average (visual calculation), and it adjusts according to the selected option. - jeroenterheerdt
Microsoft Employee
Status changed:NewtoNeeds Votes
Recent ideas
Org apps - Cannot be arranged in folders and do not stay hidden
Currently, Organizational Apps (Org Apps) are displayed in the standard Apps section of the Get Apps experience, alongside regular workspace apps. For organizations managing large-scale Power BI depl...akonda23 hours agoNew MemberNew9Views0likes0CommentsIncrease or Make Configurable the Power BI Browser Tab Limit (Currently 20 Items)
Power BI users frequently work across multiple reports, dashboards, semantic models, notebooks, and Fabric artifacts simultaneously. The current browser limitation of 20 open Power BI/Fabric items re...sharadmahajan1 day agoRegular VisitorNew339Views21likes3Comments