Microsoft Dynamics NAV 2013 Beta Available!
I don’t know about you, but I think today is a great day: Microsoft Dynamics NAV 2013 Beta has been published on PartnerSource, and if you have access, you can…
Dynamics Top 100 Nominations for 2012
It’s the fourth year of DynamicsWorld’s Microsoft Dynamics Most Influential People Top 100 list, and it’s the nomination time. Last year I’ve somehow found my way onto this list (and…
Passing strongly-typed data to Web services
Passing strongly-typed data to NAV Web services can be trickier than it seems. If you are lucky, you can make your method accept strongly-typed parameters, and you are good to go. However, if you just can’t avoid sending text data, your text must be encoded in EN-US format, otherwise it will cause problems (see this).
What the heck, just encode the data as EN-US, right? Not quite. There are a myriad of reasons why data can come in non-EN-US encoding, one of which is this: it’s the Web services, for Pete’s sake – anyone or anything can call them.
Microsoft Dynamics Mayhem
If you thought “here he comes again” with the bugs and stuff, no – this is not about it. This is just about a new sales campaign launched by PACKT…
Web Reference vs. Service Reference, Part 3
Fasten your seatbelts, you are in for the next round of Web Reference vs. Service Reference, which brings an unexpected twist to the story. After giving reasons why not to use Web References, I’ll now put my devil’s advocate’s hat on, and try to have you change your mind.
It’s simple: there are situations where Service Reference won’t work as expected, and Web Service will.
- Go to the previous page
- 1
- …
- 40
- 41
- 42
- 43
- 44
- 45
- 46
- …
- 91
- Go to the next page