The second case seems to be more interesting. The customer had found the problem himself -- a leading underscore on the ID property. As soon as he removed that, the error disappeared.
I hope this helps you resolve the error. If you still get that, please submit a regular support ticket sending a sample which we can use to investigate it locally, thank you!