Forum Discussion
DATEADD not accepting negative numbers
- 9 years ago
OKAY one of my super smart colleagues found that if we are trying to pass over the start of the year it will not work.
Today being the 31 Jan 2017, any DATEADD with a negative number that tries to go before the start of the year just returns a blank column.
Surely this is a major flaw!?
I'll relog this as an issue.
OKAY one of my super smart colleagues found that if we are trying to pass over the start of the year it will not work.
Today being the 31 Jan 2017, any DATEADD with a negative number that tries to go before the start of the year just returns a blank column.
Surely this is a major flaw!?
I'll relog this as an issue.
Has this been logged as a bug? It's almost 4 years after first surfacing this issue here and I'm now experiencing it. If DATEADD() was never intended to compute across year end/start dates then it's extremely inconvenient, but I can probably find a workaround. If It is not computing as intended then this is a bug and needs to be resolved.