Forum Discussion
#Duration function
- 4 years ago
This should do it
Add column > Custom column
[First Response Target] + #duration(0,0,[First Response Deviation in Minutes],0)
I responed to this before but deleted the post as I saw a prevoious response and thought it should work, but when I tested it it did not. I ended up with issues using the built in function since it returns a table and a single value. In any event you can use DAX and the fact that arithmatic on Date fields works with the assumption that you are using days so :
FirstResponseCalc = [First Response Target] - [First Response Deviation in Minutes]/1440
for a calculated column.
- Anonymous4 years agoNot applicable
Yes, this will work as well. This is easier than adding an additional column. If an additional column needs to be added, does that mean everytime the data set is refreshed the same column will had to be re-added?
- Anonymous4 years agoNot applicable
Mechanically, a calculated column and a column added in power query are very similar. You can use the same foumula and save a bit of memory if you use a measure, but for now I don't think you need to worry about this. As far as having to 're-add' columns I don't think you do if I understand what you are saying. The calculated Columns are calcuated and stored in memory after the Power M data is loaded, and uses a 'lazy evaluation' method (which means it is a place holder until it is shown on a visual). So you don't have to re-add it.
Of course you can test it out and see if the column stays.- Anonymous4 years agoNot applicable
Adding the additional column using the calculation for minutes was slightly more accurate on the report then doing the calculation by days in the calculated column. But the difference is fairly slim. Either one seems to work fine.
Thanks for your help as well.
Kevin