The issues you are experiencing are most probably connected to existing records in the content type whose StartTime
field is saved to the database as a common string, and not as a Date. This results in unexpected comparison of the items on their StartTime
on a database level.
You can check this by retrieving all Timesheet
items with a tool like Postman or Fiddler, and observe the JSON objects in the result. These that adhere to the structure will have a "StartTime" value in the standard UTC format "2014-04-16T08:36:20.618Z". These whose "StartTime" was not properly entered will have a value, for example, like "2014/04/16". The latter will not be evaluated as dates when making a date-based comparison.
Could you could revise the implementation of the .NET Timesheet model class and the method that inserts the Timesheets to Backend Services in regard to the proper serialization of the StartTime
property? Also, is there any cloud code relevant for the insertion of data in this content type?
If this does not solve the issues, we would appreciate if you could share the aforementioned code.