Thanks for the details. I tried the same and it works but whenever there is no Scheduled Date values it populates the value as "01/01/4713 12:00 AM". Is there any way I can get rid of it. By applying the filter >= some real date values resolves the issue, would like to know is that the right way of doing it ? or any other better way to overcome this issue ?
I am using 9104 and getting null value correctly for null date.
What version are you one?
Even I am running with 9104. Not sure why the null values are getting amended with a random date values ?
Try with other date fields e.g. completed date and see if same issue appears.
Yes. Tried with other few fields as well but no luck, all other fields as well populating that strange date value.
1 of 1 people found this helpful
I am able to replicate this as well.
Seems like a product issue where Date functions are not handling NULL properly and instead treating them as 0 leading to these Date functions returning epoch or equivalent values.
ARJDBC function FIRSTDAYOF() is returning Jan 1st 1970 if a NULL date is passed.
Similarly ARJDBC function Date() is returning this value if Jan 1st 4713 if a NULL date is passed.
Not sure why.
And if I try encapsulating this calculated field using another calculated field using case statement and NOT NULL condition, it is not returning any values!
Should be taken up with BMC I guess.
I have raised a case with BMC, will update you guys on the outcome.
Thanks for sharing the valuable inputs.