Forum Discussion
help with burndown chart
v-qiuyu-msft, I dont think that line looks quite right. Using the measure I outlined above, the result looks more like a burndown series. I have overlaid the two options for aykim101 to see:
The line needs to continually drop from 133 by the increments of the count column to end at 58 on 31 October. Make sure that Date column is formatted as a date.
Cheers,
Sam
// If this is a solution please mark as such
Hi, as MFelix and I alluded to, there needs to be a context for the calculation to take place. The calculations I outlined were in lieu of having a definned 133 so start from. You will need a table with the starting point for each of the burndown eg:
Project | Start point
Project 1 | 133
Project 2 | 150
...
Project n | value
Once you have that then and a relationship between the Project column and the Project column in your data table, you will be able to have the startpoint in your caluclation based on selection eg:
SOLVE WITH MEASURE:
Measure1:
Project Start point measure = FIRSTNONBLANK('Project Table'[Start Point],1)
Measure 2:
[Project Start point measure]-CALCULATE( SUM('Table1'[Count]), FILTER(ALLSELECTED('Table1'[Date]),ISONORAFTER('Table1'[Date], MAX('Table1'[Date]),DESC)))
Perhaps theres more to the origional post? Is the count column of the origional steps meant to sum to 133? If so then you could run a sum of the count column and use that as the starting point. =CALCULATE(SUM(Table1[COUNT]),ALL(Table1[DATE])) and use in lieu of the 133 in the calculation.
Cheers,
Sam
// If this is a solution please mark as such
Hi aykim101,
You can replace Start with "5/28/2017" and add a index column in Query Editor, then create a calculated column like below:
Burn = var Pre = LOOKUPVALUE(Table1[Count],'Table1'[Index],'Table1'[Index]-1)
return
IF(Pre=2,'Table1'[Burndown]-2,'Table1'[Burndown])
Best Regards,
Qiuyun Yu
v-qiuyu-msft, I dont think that line looks quite right. Using the measure I outlined above, the result looks more like a burndown series. I have overlaid the two options for aykim101 to see:
The line needs to continually drop from 133 by the increments of the count column to end at 58 on 31 October. Make sure that Date column is formatted as a date.
Cheers,
Sam
// If this is a solution please mark as such
thank you all for the responses but i still cannot get it to work.... so frustrating.... :-(
is there a way to sum the total of records 133 and then run the burn down?
i tried both methods and i cannot get it to work
probably needed to be more specific
small example
project | date
xyz | 5/23/17
abd | 5/30/17
das | 6/15/17
qop | 7/15/17
burndown total = 4
4 on the min date-1 (5/22)
5/23 3
5/30 2
6/15 1
7/15 0
Hi, as MFelix and I alluded to, there needs to be a context for the calculation to take place. The calculations I outlined were in lieu of having a definned 133 so start from. You will need a table with the starting point for each of the burndown eg:
Project | Start point
Project 1 | 133
Project 2 | 150
...
Project n | value
Once you have that then and a relationship between the Project column and the Project column in your data table, you will be able to have the startpoint in your caluclation based on selection eg:
SOLVE WITH MEASURE:
Measure1:
Project Start point measure = FIRSTNONBLANK('Project Table'[Start Point],1)
Measure 2:
[Project Start point measure]-CALCULATE( SUM('Table1'[Count]), FILTER(ALLSELECTED('Table1'[Date]),ISONORAFTER('Table1'[Date], MAX('Table1'[Date]),DESC)))
Perhaps theres more to the origional post? Is the count column of the origional steps meant to sum to 133? If so then you could run a sum of the count column and use that as the starting point. =CALCULATE(SUM(Table1[COUNT]),ALL(Table1[DATE])) and use in lieu of the 133 in the calculation.
Cheers,
Sam
// If this is a solution please mark as such
