Forum Discussion
How come the value is sometimes not calculated
- 9 years ago
Hi osinquinvdm,
Please modify your formula as below, this will give all the due date as expected:
Date due = DATEADD(TableName[Date created].[Date],[Delay],DAY)
Best regards,
Yuliana Gu
Hi osinquinvdm,
I believe the reason is that the date that you're trying to calculate doesn't exist in the column Date of Creation. If you look at all the dates that have been created, they all seem to fall into November but the ones that haven't are all falling beyond Novemeber and I'd be fairly willing to bet that the rest of the data in your column doesn't go past November.
Here's the link the the DAX function definition:
https://msdn.microsoft.com/en-us/library/ee634905.aspx
There's a line in there that states:
The result table includes only dates that exist in the dates column
I'm hoping that someone better than I will be able to provide you with a solution on how to get round it!
Good luck!
- fiveone9 years agoHelper II
Good catch eyeball on the function disclaimer in the DAX documentation.
I'm not a big fan of * and small fonts, I'm more the type of guy who does not go though contract details and jump directly to the signature page :-)
You are right, that test dataset is full of holes in terms of dates - so yes those dates where not part of the original date lists.
Anyway if that is the way dateadd() works I have no choice but do the work in the query. Which works fine (see below DAX calculation has been renamed date cible/target and M calculation is called date due).
Thanks so much for the quick follow-up (and attention to details)