List data validation failed when creating a new list item but does not fail when editing an existing item

Question

Dear SharePoint Experts,
Please help.
Why does my simple formula work in Excel but not-work in SharePoint?
Why does this formula...
=IF([Request Type]="Review",(IF(ISBLANK([Request Date]),FALSE,TRUE)),TRUE)
...work in Excel but fail when I try to use it in SharePoint?
The intent of this formula is the following...
If the field "Request Type" has the value "Review" and the field "Request Data" is blank then show FALSE, otherwise show TRUE.
SharePoint saves the formula, but when a list item is saved where the formula is implemented, (under List Settings, List Validation), SharePoint does not, say anything other than that the formula failed.
Note that the "list data validation failed" error only happens when I am creating a new item-- the formula above works just fine when one is trying to Save on the edit form. 
Can you help?
Thanks.
-- Mark Kamoski

Answer 1

Dear Jason,
I appreciate your efforts.
However, it seems to me that this statement of yours is not correct...
"If it meet the validation formula, then you can new or edit the item, otherwise, it will throw the 'list data validation failed' error, it is by design".
I believe this is NOT the answer for the following reasons.
When I create a new item and click Save, the validation error is "list data validation failed".
When I edit an existing item and click Save, the validation error is "my custom error message" and this is, I believe, the way it needs to work each time.
I think, at the core, the error my formula does not handle some condition of null or blank or other default value.
I tried a forumla that casts the date back to a string, and then checked the string for a default value, but that did not work.
I tried looking up the Correlation ID in the ULS when "list data validation failed" occurs, but that gave no useful information because, even though logging was set to Verbose, the stack trace in the error log was truncated and did not given any
good details.
However, it seems to me that SharePoint 2013 is not well-suited for complex validation rules, because...
SharePoint 2013 list-level validation (NOT column-level validation) allows only 1 input for all the multi-field validation formulas in a given list-- so, if I had more than 1 multi-field validation rule to implement on a given list, it would need to be packed
into that single-line-of-code forumla style, like Excel does. That is not practice to write, debug, or maintain.
SharePoint 2013 list-level validation only allows 1 block of text for all such multi-field validation rules. So that will not work because I would have something like "Validation failed for one or more of the following reasons-- withdrawal cannot exceed
available balance, date-of-birth cannot be after date-of-death,... etc". That will not work for me.
The real and awesome solution would simply be enhancing SP 2013 so that column-level validation forumlas are able to reference other columns.
But, for now, my workaround solution is to use JavaScript and jQuery, hook the onclick handler on the Save button, and that works good. The only problem, is that the jQuery validation rules run before any of the column-level rules created  with OOTB
SP 2013. So, in some cases, there is an extra click for the enduser.
Thanks,
Mark Kamoski
-- Mark Kamoski