I noticed that when I try to save an observation whose Concept is a “DateTime” of class “Misc” via the Web Services, it fails. If I use a different DateTime Concept of type “Question”, it works!. The failure is caused by a date format parsing issue. The class “Misc” doesn’t like the format that I am sending of “2017-02-01T00:00:00.000-0500”.
@jcelano as Wyclif says, nothing in the code cares about concept class when saving obs. (We do switch on the concept datatype.) There must be some other difference between those two concepts…
Actually, looking more closely at the Concept types, the one that works is Date, while the one that fails is Datetime. Is there a different format for Datetime?
A quick fix would be in the REST module so that it parses the date and sets it via Obs.setValueDatetime() or Obs.setValueDate() instead of Obs.setValueAsString(), then we can also have it addressed in core as a longer term fix.