Get certified in Microsoft Fabric—for free! For a limited time, the Microsoft Fabric Community team will be offering free DP-600 exam vouchers. Prepare now
Hit "Reply" and let us know what you think of visual calculations! To learn more about this feature, please visit the blog post or our documentation.
Here are some areas that we'd like to hear about in particular:
Thanks and we look forward to hearing your feedback!
Yes i found it in the start ribbon.
I thought i should find it in the modeling tab.
But now i know where to find it.
Thank you!
Hi. I think that we will find a couple of usecases for this new feature!
I'm learning with it and have found a few areas that deserve improvement. First of all, there's the edit call for the visual calculation - I seem to have to click too much before I get to the actual editing. Wouldn't it be enough to double-click on the title, for example? The second thing - as soon as I fail to enter the calculation correctly, the whole visual disappears and suddenly I can't see what columns I can use in the calculation - wouldn't it be enough not to display just that one column? Also, it would be nice if the calculation in a given column could somehow be easily viewed without having to call its editor (mouse-over?).
Thx, JJ
double-click has traditionally be reserved for rename, so we can't really use that.
Regarding the error blocking the whole visual, that's on the list to improve.
And then in regards to your third suggestion, are you thinking about having a mouse-over outside of the visual calculations edit mode and then showing the DAX?
Regarding info about future improvement - nice, thx 🙂
Regarding my suggestions - I have no ambition to propose a final solution, rather I was thinking how to work with something better 🙂 But yes, the 3rd idea was about showing DAX formula for visual calculation in editor mode & "mouse over" event 🙂 Whan I thinking and trying this new feature maybe the was to editing the visual calculation could be in the "same way" as on-object interaction rather than new way - i.e. when I starting to edit visual i am able to change visual behavior / appearence & visual calculations ?
But either way - I look forward to further developments and improvements 🙂
those are great suggestions and ideas! I added this to the list of input to consider. Really appreciate the time and effort
Thx 🙂
I'm trying to imagine how I would like the Visual Caculations editor and send some visual results of my thinking 🙂
JJ
thank you - out of these things, if I am not mistaking all things are currently already the behavior, with the exception of not being able to click on the visual matrix header to edit the visual calculation. That is coming though. Am I missing something?
I hope you didn't miss anything and I look forward to more improvements in March 🙂
I've already got a win from this. There was a requirement for a specific dimension to count its items without disambiguation. So, a matrix with measure totals one way and visual totals the other. This could probably be solved before, but I'm never sure I've done a filter manipulation right or if I've left myself some surprise for later.
Hopefully the restrictions will fall, in particular export will be something that will mean a few places I could have used this will have to wait. I was hoping to crack on with conditional formatting - my model has plenty of measures which format a single visual and it would be nice to clear those up. I can work around this more easily.
One concern is that I would like to maintain visibility into what I've written. DAX Query View has finally made it easy to look after measures and columns. The ability to have visibility into what I've written would make me more confident in using the feature.
I'm also wondering if hidden columns in general could piggy-back off this feature? I'd love to hide the ugly compound keys that power drill-through pages.
hello and thanks for the feedback. It's great to hear you are making good use of this already! Conditional formatting is absolutely on the list of things we want to work on. On top of that, we are using visual calculations as a way to develop new functionality and paradigms and plan to evaluate what we build there to see where it might apply to the rest of the product. Hidden is a prime example of that.
What are you thoughts on what you'd like to see for the visibility you mentioned?
I've already mentioned a drill-through column that does not need to be visible. As well as inside the visual, this also affects exports. Some people will use white text as a work-around to achieve a "hidden" column visually, but then the data appears in the exports.
Sometimes, I want to force all rows to appear - Power BI will automatically collapse rows that are the "same" which is correct for summaries but less useful when investigating the data. Having a hidden key field would ensure rows are separate while leaving the space for columns related to the investigation.
When using columns in cell elements like "Web URL" from a related table, this does not work correctly if no columns from the related table are in the table visual and the columns are only used in the elements. Having a hidden column from the related table would force a correct model and allow the use of these fields. Currently I'm duplicating the column in my main table.
One way of sorting on multiple columns is to create a compound sort key and use that as a column. While full sorting would be better, these columns would be better hidden when they are used.
I've previously taken some notes on this based on the Ideas site. Other requests I've seen include:
thank you. we are working through the export story at the moment, so this is really useful input.
Hidden is a prime example of that.
For me this discussion is similar to the one we had when windowing functions were new. With the difference that those do allow you to reach back into the data model.
Is it already mentioned anywhere that hiding fields only seems to be possible with On-Object enabled?
that's not supposed to happen. I can hide fields fine without on-object on. Can you show a screenshot?
Oh. You can only hide the visual calculations, not the other columns?
you can't hide columns that are used as groups, but you can hide numerical columns (implicit measures, explicit measures, calculated columns and visual calculations)
How do you hide calculated columns? When creating a table visual, I am only able to hide a calculated column if it is aggregated (for example choosing Count or Average instead of Don't summarize) even if the calculated column returns a numeric value. I can hide measures and visual calculations just fine, though.
I get it. No, you can't hide an unaggregated calculated column, because that is then being used as a group not a detail. if you add an max aggregation for example you can hide it just fine. the core difference is not that this is a calculated column, it's about how you use it: a group vs a detail. You can't hide grouping columns.
First of all, what a great feature! I have been waiting for this, for a long time. Well done!
Right now it seems that I am not able to reference any of my measures of the model in my visual calculation.
I would like to be able to add a calculation that is only used in the specific visual.
For instance, I have a measure [Turnover] in my model. I have a table that needs to show turnover / 1000 per region.
Right now I have to add the [Turnover] measure to the table and hide it. Then create a visual calculation: Turnover / 1000.
Would be a lot easier, if I could just use the [Turnover] measure in my visual calculation straight away.
Hello and thanks for checking in. What you mention is in fact by design and kind of the point of this feature. You can't refer back to the model because it would bring back the complexities we're trying to "leave outside". Just bringing in the measure easily resolves this as you have discovered.
Thanks for your reply. I totally understand that you are trying to hide the complexity. I actually expected that you would give me the "by design" answer. 😊
However, I do feel that it has added value to be able to reference the measure from the model. Perhaps a new function could still hide the complexity, but allow expert users to use measures from the model. This way you don't have to pollute the visual with columns you have to hide.
For instance take the following visual calculation : MEASUREFROMMODEL('[Turnover]') / 1000
The MEASUREFROMMODEL function allows me to get a measure from the model. This way you still hide the complexity from basic users, but an advance user can get measure from the model.
Check out the October 2024 Power BI update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.
User | Count |
---|---|
113 | |
89 | |
84 | |
76 | |
64 |
User | Count |
---|---|
136 | |
111 | |
98 | |
97 | |
92 |