Proper handling of return values for formula UDF date functions
Right now:
"Any formula that supplies an invalid date to the Date function will result in a blank value. For example, the function “Date (2012, 4, 31)” is invalid since the month of April does not have 31 days. If this function is part of a larger compound expression, the entire expression will evaluate to blank."
Adding a IsBlankDate() predicate function would go a long way to allowing formula UDFs to track blank date fields and respond accordingly.
-
Robbie Brand - Collier Pickard commented
Some way to determine that a date is null/blank/invalid would help.
It seems that Maximizer evaluates all parts of an IF statement before running it and if any part returns null the whole thing returns null.
So if IsDate() or IsNull() functions were added and properly evaluated it would help a lot.we get a lot of [If (Date1 > Date2,...,...)] or [If (Date1 is Null, use Date2, else use Date1)] types of formula queries. But none of these can be done if either date is null.
Can a date formula field allow a blank/null return? Something like
[If (FieldX == "value a", Date1, Null())]Another useful function would be DateAdd(), like SQL has so you can add/subtract a number of years, months or days from another date. we can add days by adding the number of days to a date field