Hi Jofry, In most circumstances, Health is flexible about the CCR it accepts. However, if you are specifying a DateTime, then Health is currently expecting to see an inner ExactDateTime element. Having an ExactDateTime *and* an ApproximateDateTime works, since the latter will be ignored. I've created an issue for this since we may want to re-evaluate this logic. Please be sure to star the issue and add comments if necessary. In the near-term, however, you'll need to ensure you have an ExactDateTime element (a 'sed' replacement, Java replaceAll, etc.), or remove the DateTime altogether.
Issue: http://code.google.com/p/gdata-issues/issues/detail?id=2407 Thanks a lot for bringing this to our attention. I'll be sure to update this thread and the issue once there is progress. Paul (Google) On Nov 22, 8:04 pm, Jofry Sutanto <[email protected]> wrote: > Hi all, > > I've had no problem so far in downloading CCR from h9 service using > ClientLogin, but I've got a problem when uploading one. Apparently if > I uploaded CCR that uses <ApproximateDateTime> instead of > <ExactDateTime> i'll receive error from h9 service. While I know the > documentation stated only <ExactDateTime> is supported at the moment, > I was expecting h9 to just ignore the value and keep whatever > information that conforms with Google Health standard. Is there anyway > to get around this issue, as I'm getting CCR (complete CCR, not Google > health subset CCR) from other places and would like to upload them to > h9. > > Many thanks in advance for the help. > > Regards, > Jofry -- You received this message because you are subscribed to the Google Groups "Google Health Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/googlehealthdevelopers?hl=en.
