Anyone else have this issue? Any workarounds, aside from not using metadata?

Oct 4, 2012 at 2:12 PM

I posted a new issue here:

Anyone else have this issue and know of a workaround or temporary fork that handles this? For now I have to work without metadata and manually parse out properties that would have been parsed for me by datajs if it had metadata. Also I don't get full validation in either direction.

Oct 4, 2012 at 7:09 PM

Hi SleepyDaddySoft,

     Thanks for reporting this. We will fix it and will get back to you with a workaround.  Could you please let me know which version of datajs are you using, 1.0.3 or 1.1.0-beta?


Alex Trigo.

Oct 4, 2012 at 7:22 PM

1.1.0-beta. Thanks for the followup!

Oct 5, 2012 at 7:19 PM

Awesome, thanks.  A new beta is scheduled to go out next week, we will include a fix for this.  In the meantime can you use ATOM instead of JSON?


Alex Trigo.

Oct 5, 2012 at 7:31 PM

I'll just work without metadata in the meantime - it seems to be working fine so far.

Unrelated question: Does datajs support the new JSON Light format in OData V3? I would like to move to that format as soon as that makes it into a stable release of WCF Data Services.