Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hello Friends,
New to PowerBI.
Currently i want to compute the YTD volume (example July 2024 - Feb 2025)
I already have a DAX function for the volume
Solved! Go to Solution.
Its difficult to suggest any change without knowing the data model and sample data. But I will suggest
First rewrite the 'Sum of KG measure'
SUM OF KG =
SUMX(
ItemMaster,
( (ItemMaster[ Quantity ] * -1)* RELATED('Item'[ MAP VOL ] )
)
You can reuse it in the YTD measure like this
FYTD_SumOfKG =
VAR PreviousWorkingDay_ = DATEVALUE([PreviousWorkingDay])
VAR FiscalYearStartDate_ = DATEVALUE([FiscalYearStartDate])
RETURN
CALCULATE
(
[Sum of KG],
FILTER(
ItemMaster,
DATEVALUE(ItemMaster[Physical date]) >= FiscalYearStartDate_ &&DATEVALUE(ItemMaster[Physical date]) <= PreviousWorkingDay_) ,
REMOVEFILTERS('calendar'[Year],'calendar'[Month Name])
)
Intead of the above pattern I woud suggest you to use time intelligence function like DatesYTD and pass the second parameter to last date of the financial year.
FYTD_SumOfKG =
CALCULATE
(
[Sum of KG],
DATESYTD(Calendar[Date], "6-30")
)
For further assitance please share the pbix file
Need a Power BI Consultation? Hire me on Upwork
Connect on LinkedIn
|
Hi @PowerDev1977 ,
I am happy to learn that you found the cause of the problem and fixed it.
Please accept @tharunkumarRTK 's reply as a solution, it will make it easier for other users who may be experiencing the same problem to find a solution.
Thanks for your understanding.
Best regards,
Lucy Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Its difficult to suggest any change without knowing the data model and sample data. But I will suggest
First rewrite the 'Sum of KG measure'
SUM OF KG =
SUMX(
ItemMaster,
( (ItemMaster[ Quantity ] * -1)* RELATED('Item'[ MAP VOL ] )
)
You can reuse it in the YTD measure like this
FYTD_SumOfKG =
VAR PreviousWorkingDay_ = DATEVALUE([PreviousWorkingDay])
VAR FiscalYearStartDate_ = DATEVALUE([FiscalYearStartDate])
RETURN
CALCULATE
(
[Sum of KG],
FILTER(
ItemMaster,
DATEVALUE(ItemMaster[Physical date]) >= FiscalYearStartDate_ &&DATEVALUE(ItemMaster[Physical date]) <= PreviousWorkingDay_) ,
REMOVEFILTERS('calendar'[Year],'calendar'[Month Name])
)
Intead of the above pattern I woud suggest you to use time intelligence function like DatesYTD and pass the second parameter to last date of the financial year.
FYTD_SumOfKG =
CALCULATE
(
[Sum of KG],
DATESYTD(Calendar[Date], "6-30")
)
For further assitance please share the pbix file
Need a Power BI Consultation? Hire me on Upwork
Connect on LinkedIn
|
Thanks Tharun,
Actually this is what i did and it worked.
I have another issue which i would like to have your guidance.
I have my budgeted sales table which is linked to my calendar table. However , i want the match to be done on the month rather than date. i have inserted firstdate of the month for the Budgeted sales month so it is normal calendar will not find all the the dates, i want the matching to be done on the month rather
example
Budgeted Sales table contains
Date Month Sales
01/01/2025 1 2000
01/02/2025 2 3000
Now calendar contains
Date workingDayRank NumberOfDays month
01/01/2025 24 1 -- working day rank empty since non-working day
02/01/2025 24 1 -- working day rank empty since non-working day
03/01/2025 1 24 1
04/01/2025 2 24 1
I have to perform a calculation for each row (and i need to ignore the relationship on date)
sales prorata = (sales * workingDayRank )/NumberOfDays
Used below, but still it ignore January cause it seems it is still matching on the date.
Glad to know that you are able to implement the approach suggested.
I would request you to create a new thread for this new question
Need a Power BI Consultation? Hire me on Upwork
Connect on LinkedIn
|
User | Count |
---|---|
25 | |
12 | |
8 | |
6 | |
6 |
User | Count |
---|---|
26 | |
12 | |
11 | |
10 | |
6 |