[
https://issues.apache.org/jira/browse/OLINGO-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306401#comment-15306401
]
Rahuldeb Barman commented on OLINGO-961:
----------------------------------------
We are building connectivity to SAP C4C and we are currently blocked by this
issue.
Most of the date-offset values from SAP C4C are returned in this format and as
there is no way to avoid/work around the validation process, it is blocking us
from getting or showing the data as a result of the query.
Also almost all the entity has this field so we are not able to get/retrieve
most of the entities.
A quick turn around on this issue will be highly appreciated.
Thanks,
Rahul
> Higher precision support for DateTimeOffset
> --------------------------------------------
>
> Key: OLINGO-961
> URL: https://issues.apache.org/jira/browse/OLINGO-961
> Project: Olingo
> Issue Type: Bug
> Affects Versions: V2 2.0.7
> Reporter: Sagar
>
> I am getting '2016-05-23T11:51:00.8398830Z' string from SAP OData endpoint
> for the Edm.DateTimeOffset data type field.
> I believe that this is valid format as per the
> http://www.odata.org/documentation/odata-version-2-0/overview/ (# 6.
> Primitive Data Types).
> Looks like the apache olingo 2.0.7 version is not able to parse this valid
> DateTimeOffset String.
> Isn't '2016-05-23T11:51:00.8398830Z' is valid format for Edm.DateTimeOffset
> data type?
> For more details refer my last 2 comments on
> https://issues.apache.org/jira/browse/OLINGO-749
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
