Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
I have a project where I need to find the average number of movies each actor/director pair has done during the director's longevity for all Netflix directors.
I broke down my formula to find out why I can't get the right answer and I found out that when trying to find the director's longevity the result is rounding to the nearest whole number in years instead of 1.47 years or .62 years or the like.
This is just one iteration of my attempts to produce a decimal.
DirectorDuration =
VAR __Table =
SUMMARIZE(
'Netflix',
'Netflix'[director],
"FirstDate", MIN('Netflix'[date_added]),
"LastDate", MAX('Netflix'[date_added])
)
RETURN
SUMX(
__Table,
DATEDIFF(
DATE(YEAR([FirstDate]), MONTH([FirstDate]), DAY([FirstDate])),
DATE(YEAR([LastDate]), MONTH([LastDate]), DAY([LastDate])),
YEAR
)
)
I have also tried a few variations of using DAY / 365.25 and still get whole numbers (or 0s if it's less than a year). How do I go about getting some fractions!?
pls try this
DirectorDuration =
VAR __Table =
SUMMARIZE(
'Netflix',
'Netflix'[director],
"FirstDate", MIN('Netflix'[date_added]),
"LastDate", MAX('Netflix'[date_added])
)
RETURN
FORMAT(SUMX(
__Table,
DATEDIFF(
DATE(YEAR([FirstDate]), MONTH([FirstDate]), DAY([FirstDate])),
DATE(YEAR([LastDate]), MONTH([LastDate]), DAY([LastDate])),
YEAR
)
),"#,##0.00")
Interesting that your solution which looks like it forces the decimals goes back to a whole number! (DirectorDuration2)
I appreciate the help nevertheless.
I fixed it, check again
"#,##0.00"
Unfortunately, it's still giving me 1.00, 0.00, etc. Appreciate the attempt!
I ran into the same issue a while back. The fix for me was simple - select the measure, go to the "Measure Tools" at the top, and make sure that the data type is set to decimal number, with the number of decimal points you want.
I got excited, but alas that didn't solve the issue. Now the results are "1.00, 0.00, 0.00, etc."
For example the data here for Alastair Fothergill shows a longevity of 5.00, but it should be 5.44 based on Aprill 22, 2015 through October 04, 2020.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.
User | Count |
---|---|
143 | |
85 | |
66 | |
51 | |
45 |
User | Count |
---|---|
216 | |
89 | |
82 | |
66 | |
57 |