2 min read
BizTalk Orchestration – Call Orchestration from another project or from another BizTalk Application
Sandro Pereira
Jul 24, 2009
As your BizTalk environment grows, you shouldn't reinvent the wheel If you have a common error-handling or logging orchestration, you should call it from
3 min read
There was a failure executing the send pipeline: “Microsoft.BizTalk.DefaultPipelines.XMLTra...
Sandro Pereira
Jul 24, 2009
When trying to receive an XML document from a Receive Port, the following error message occurs, and the message is suspended: “… Error Description:
2 min read
Problem with Edifact Interchange and loopback adapter Receive Pipeline – Received unexpecte...
Sandro Pereira
Jul 24, 2009
In a previous project, I worked with EDI messages to interchange with partners, but before I sent the message to the partner, I needed to pass it through a
3 min read
BizTalk Document Mapping – Mass Copy Functoid
Sandro Pereira
Jul 20, 2009
Mapping large XML documents field by field can be tedious and error-prone When you have two schemas with identical sub-structures, the Mass Copy Functoid is
4 min read
BizTalk Document Mapping – Value Mapping Functoid and Value Mapping (Flattening) Functoid
Sandro Pereira
Jul 20, 2009
The Advanced Functoids category in the BizTalk Mapper contains two tools that look almost identical: Value Mapping and Value Mapping (Flattening) While they
3 min read
BizTalk Schema validation – Default and Deep Validation
Sandro Pereira
Jul 20, 2009
One of the most common misconceptions for new BizTalk developers is assuming that if a message passes through a pipeline, it must be valid according to the
4 min read
BizTalk Document Mapping – Organizing Maps
Sandro Pereira
Jul 20, 2009
As any BizTalk developer knows, what starts as a simple "drag-and-drop" map can quickly spiral into a "spaghetti" of links that is impossible to debug When
3 min read
Introduction BizTalk Document Schemas – Part II
Sandro Pereira
Jul 4, 2009
If the Root Node is the "Name" of your message, the Namespace is its "Surname" In a global enterprise environment, you might have ten different "Invoice"
