Improved error message handling for datetime conversion failure
Library errors out unexpectedly in a scenario when datetime conversion is trying to happen on a json object instead of a string of some date format. This is a user error that ends up in a 500 when Storage API to fetch records is called with conversion enabled.
Example is added in the unit test which generates this issue.
We should handle it with a proper error message instead of failing with 500