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.
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.
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
70 | |
68 | |
43 | |
34 | |
26 |
User | Count |
---|---|
86 | |
50 | |
45 | |
38 | |
38 |