REST JSON Christmas Puzzle
If I use the BizTalk 2013 R2 JSON Encoder pipeline component to convert the following XML <ns0:ASCIISchema
Authenticating Salesforce REST API calls to custom Apex endpoints
Seroter has shown us how to call the Forcecom REST API from BizTalk Server and we used this to successfully call standard Forcecom objects like
BizTalk 2013 R2 JSON Encoder error – “Object reference not set to an instance of an o...
In a previous post I lamented that the JSON encoder pipeline component throws an error if a soap fault is sent to it My colleague Deepa Kamalanthan has
BizTalk 2013 R2 JSON Encoder error – “Object reference not set to an instance of an o...
We have discovered that if a SOAP fault is sent to a pipeline using the JSON Encoder the following error occurs; A response message sent to adapter
Using BizTalk 2013 R2 to transform an XML message element to a JSON array
I wanted to know whether the out of the box JSON encoder pipeline component creates an JSON array if there is only one repeating XML fragment One of my
XSD chokes when using hyphen in element name – “Specify a valid .NET type name for th...
I just got caught with this The solution is to remove the hyphen from the Rootnode TypeName property in the BizTalk schema
The BizTalk Health Monitor Snapin Errors on Installation of BizTalk 2013 R2 Cumulative Update 1
After installing the CU1 update we observed this error from the BizTalk Administration console We attempted to register the new MBVSnapindll using
SOA Patterns with BizTalk Server 2013 and Microsoft Azure – Second Edition
I am pleased to announce “SOA Patterns with BizTalk Server 2013 and Microsoft Azure - Second Edition” by Mark Brimble, Johann Cooper, Coen Dijgraaf and

