Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hello,
I have an issue with the running total for Last Year... that doesn't stop running. I've looked for a whole day on the forum, tried lots of things but can not find the solution.
What I want to see is for a specific pickup month (in this case March2019, filtered on the left) to track the reservation pattern per booking calendar week next to the pattern of last year. The tricky part of my issue is: I am having two date tables 'Date Pickup' and 'Date Booked'.
On the left you can see that I am filtering on pickup year and month from the date table ''Date Pickup'. In the table you see the WeekNumYear which is based on the date table ''Date Booked''. RezReporting is the main table with all information per reservation.
These two formulas work perfect as expected for the current year:
Res Nr = COUNTROWS(RezReporting)
Solved! Go to Solution.
Sure, so I've not sure what the date column is called in your 'Sheet1 (2)' table, but to do this all in a measure the code would look something like the following:
This article shows how to prevent displaying future dates for cummulative calculations
https://www.sqlbi.com/articles/hiding-future-dates-for-calculations-in-dax/
Can you show me what and where to put in my measure?
if i want to show running total util the last day?
Sure, so I've not sure what the date column is called in your 'Sheet1 (2)' table, but to do this all in a measure the code would look something like the following:
Thank you for your help!
I found a solution, a similar idea to what you propose by finding a min and max date and filter based on this. This is now my measure:
Aweseme I got a desired result with your answer.
To get the aswer, we need 4 measrues, correct?
@colourfullife wrote:Aweseme I got a desired result with your answer.
To get the aswer, we need 4 measrues, correct?
I'm not sure what you mean here, the code above is one measure, it's just broken down internally into 4 variables. You could probably do the same thing in one large expression, but variables typically make it easier to break the logic into smaller parts so it's easier to read (and it often improves performance as variable values can be cached internally)
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
111 | |
100 | |
80 | |
64 | |
58 |
User | Count |
---|---|
148 | |
111 | |
93 | |
84 | |
66 |