Forum Discussion
Time series
- 2 years ago
The Time value will be represented by a decimal number behind-the-scenes and the Generateseries algorithm, at some point, is losing something when translating between decimals and time values. That's my best guess.
Maybe one way to solve this is to replace the TIME with your own decimal. I think
0.041666667 / 4might work but you'll need to test at your side.
0.041666667 is the decimal representation of 1 hour, (1/24) but with some rounding applied.
It will still break at some point if the sequence is long enough (i.e. more years in the sequence).
----
My solution is just a workaround really. Maybe there is a better way of doing it (Power Query probably)
The Time value will be represented by a decimal number behind-the-scenes and the Generateseries algorithm, at some point, is losing something when translating between decimals and time values. That's my best guess.
Maybe one way to solve this is to replace the TIME with your own decimal. I think
0.041666667 / 4
might work but you'll need to test at your side.
0.041666667 is the decimal representation of 1 hour, (1/24) but with some rounding applied.
It will still break at some point if the sequence is long enough (i.e. more years in the sequence).
----
My solution is just a workaround really. Maybe there is a better way of doing it (Power Query probably)