The bug with which I started this series is nothing critical. It manifests rarely, you can easily work around it. It’s in the “so what” category.
But the one I’ll talk about today is a tough beast, with not-so-easy workarounds that cause as much headache as the bug itself.
So, here comes bug #2: setting a date to 0D.
If something, Stratus has taught me how buggy the implementation of Web services in Microsoft Dynamics NAV is. Let me be clear from the onset: Web services are a great functionality in NAV, one of the best additions (together with .NET interop) to NAV stack in a long while. But it’s buggy.
Being buggy doesn’t mean it doesn’t work. It only means you need to twist and bend your code to achieve things which you would expect to work out of the box. During development of Stratus, we had to make a series of workarounds in Web services to achieve simple goals, and I decided to share those bugs (and workarounds) with you, to help you be more productive in your Web services based projects.
So, here we go for bug #1: lowercase codes in primary key.
A couple of days ago, at a Sure Step 2010 training at Sundsgården, Helsingborg, Sweden, while students were preparing to take the exam, one of the students asks me where she can download Sure Step 2010. I give her the link, but she tells me: “No, that’s Sure Step 2012, I’d like to download 2010”.
That came as a surprise. “No way” – I say – “It hasn’t yet been released.”
Or has it?
And then I check, and almost can’t believe it – it’s really there. I completely missed the tweets, the Facebook announcement, the LinkedIn discussions. It seems that I’m not particularly social nowadays. A quick check of Twitter shows me that there wasn’t too much buzz around it, and most of the blogosphere simply redelivers the same content, which either comes from the official announcement (which I also missed 
) or from whoever blogged first.
Instead of giving a simple “excited” redelivery of the announcement, here’s my take on Sure Step 2012, what’s new, what’s not new (both sadly and thankfully).
If there wasn’t one already, someone should have invented Belgium. There are two things in this world that I love, and probably shouldn’t (and an oversized red speaker’s shirt I got from Luc today did a darned god job at concealing the unlucky consequences of overly indulging in both of them): beer and chocolate. Boy, do Belgians know their beer and chocolate!But they know their NAV, too, and after NAV TechDays 2011, which have just ended in Antwerp, and two days of top NAV content, I can only say – great job, Luc and the team, and please make it a tradition.
If you attended my presentation about .NET interoperability, then there are a couple of demos I couldn’t deliver due to time constraints, and I promised to blog it. So, here we go.
It’s about streams. You already know that in NAV there are two data types, InStream and OutStream, that allow you to stream data in and out of generic sources or destinations. They are a fantastic tool, because they require you to know nothing about the type of source or destination, and you can store and retrieve data without having to care if the data comes from Internet, or a BLOB field, or is it written to a file, or transported over an XMLport. Stream makes it abstract and allows you to simply handle the data, and make the object itself care about the specifics.
Today, Stratus has officially entered the pilot phase in Latin America, after the latest build of Stratus Setup Wizard has smoothly and flawlessly configured Stratus in a local customized version…