Forum Discussion
Measures Contain Different Values on Table View and Visual View
Hi,
I'm using the dates from a transaction table as measures and then using them in my column. My measures look good in the visual view, I've called them RD1 and RD2 based on a column "RD". However I'm finding them inconsistent when used in my table. Here is my definition for them, the values get shown as I'd like in the visual view:
However, in the column/table view these never change, they only reference the first and last dates in the table from which they're pulled (RD column). Why doesn't this flow back to the table view (note that I added a column just to show what the measures were as I worked through.
3 Replies
Hi,
I'm experiencing an issue where my measures are inconsistent between the table view and the visual view. I created two measures for beginning and end dates, RD1 and RD2. Below shows them with different values depending on where I look. Is this the expected behaviour?
This is the difference between calculated measure and calculated column.
Calculated columns (and tables) are:
- Evaluated for each row in your table, immediately after you hit 'Enter' to complete the formula
- Saved back into the model so take up space
Calculated Measures are:
- Evaluated when you use it in a visual, when the visual is rendered
- Not saved anywhere (well, actually there's a cache in the report layer but it's not part of the file when you hit Save)
Please refer to the link below to see the details.
http://www.sqlbi.com/articles/calculated-columns-and-measures-in-dax/
https://projectbotticelli.com/knowledge/dax-calculated-columns-vs-measures-video-tutorialRegards,
Charlie Liaov-caliao-msft
Thanks for the feedback.Do you have any recommendation for how to take a value defined in a visual and using it in a column calculation then? Or is this not something Power BI can do?
