From the Microsoft Dynamics NAV Blogs: Web Services Bug Theater; QR Codes in NAV Docs; Improve Your Cash Flow with Reminders; SOD December 2011 Update

Web Services Bug Theater Series: Recently on his Navigate into Success blog, NAV MVP Vjekoslav Babic reviewed his experiences dealing with some of the bugs in the Dynamics NAV's web services.

Babic says that during the development of the Stratus web client for Dynamics NAV,  the developers had to make a series of workarounds to achieve simple goals. Babic decided to share those bugs (and workarounds) to help you be more productive in your Web services-based projects.

The first bug Babic mentions is "lowercase codes in primary key," which requires the developer to take the extra step of setting codes to upper case before shipping them over to NAV. RTC seems to do just that, he adds.

This bug is really not critical. It doesn't even show up often and you can easily work around it. It's in the "so what" category, Babic says.

Not so for the next bug Babic highlights, which he admits is "a tough beast, with not-so-easy workarounds that cause as much headache as the bug itself"-"setting a date to 0D."

The problem is when you expose a page that includes a date field, as a web service, there's no way you can set it to 0D value. He says NAV simply keeps the value as it was earlier. So, once you write a date, it's there to stay.

Babic says to workaround this issue, you'll need to write some kind of a function that "you can call, and tell it which date field in which table, for which record, should be set ...