In my country, there’s a saying: “A good horse has a hundred flaws; a bad one has only one.” It’s bad.
People have asked me why I am doing this, and if I hate Web services because I’m blogging about their flaws. In fact, I love Web services, and as I said in the first post in this series – they are great. They are a good horse. A winner.
The reason why I am doing this is because I want to share the problems I encountered over months of working with Web services intensively, as well as the solutions or workarounds I identified.
Today, on the repertoire we have another security-related glitch, which has been confirmed to me by Microsoft, but as far as I know there has not yet been a hotfix for this.
Bug #4: accessing Web services in multi-company scenarios.
“Are we all in” – asks Hunter Richards on The Software Advice blog in his Monday post, giving a view of Microsoft’s Cloud strategy in perspective of Microsoft Dynamics. He argues that while Microsoft is indeed betting heavily on the Cloud, its Dynamics line of products is not nearly ready for the Cloud.
In his argumentation, Hunter gives four challenges that Microsoft is facing, and that are main obstacles in Microsoft’s way to Cloud Dynamics ERP: architecture, multiple products, partner channel and market readiness.
I believe in the Cloud. And I believe in Microsoft Dynamics ERP in the Cloud. So I do not agree with Hunter’s views on this, and here I’m offering a counter view. Okay, I must say that my views are limited exclusively to NAV, so whatever I say applies to NAV, and may not apply to AX, SL or GP.