Browse by Tags

Recently I was testing a BizTalk map inside Visual Studios. The input schema was auto generated using the SQL Adapter and the output was a simple text file. I was using a sample file provided to me from a past generation from the schema (or so I thought) to test the map. When I was testing, I keep getting...

Carlos Medina has created a functoid that can be used to extract context values from a message inside a map! This is a very common problems and this approach is something I didn’t really consider. Make sure you check out his post . He has sample code and the solution for download.

In a past edition of The BizTalker , I talked about how easy it is to use custom XSLT inside the BizTalk Mapper to sort data. Sorting data inside the map can be doing using inline XSLT like this: <xsl:for-each select="Record"> <xsl:sort select="Id" data-type="number" order="ascending"/> <xsl...

I should start by saying I was much happier with last year’s entry . Last year, I used an Orchestration to limit other running Orchestrations. It could be configures on the fly using the Rules Engine. I should note that in Biztalk 2006 you will now have the ability to limit running Orchestrations...

Dynamic mapping is the concept of specifying the map to be used for a transform at runtime inside the orchestration. That means no Transform Shape is used to specify the map or input and output schemas. The help guide talks about dynamic mapping. It is under the heading “ Assigning to Transforms...

Biztalk Server 2006 introduces many exciting new features like Recoverable Message Processing and Suspended Message Routing . With great new features like these, sometimes the map and schema editor improvements can get overlooked. Anyone that has worked with Biztalk 2004 maps has probably seen this message...

Message context is a critical part of message routing and processing inside BizTalk Server 2004. How this context is handled during mapping is different depending on the location of the mapping. The context is copied differently using Receive Port mapping verses Orchestration mapping. Why should you...

This is a cool feature of BizTalk 2004! It allows you to map many documents into one or map one document into many. In either case, your inputs will not equal your outputs. This type of mapping does require some up front planning and careful consideration. First off, this type of mapping is only allowed...

Recently on a project I was required to filter out single records from a large batch that were not required to be processed inside the business process. In this case, the vast majority of the thousands of input records would not be required in the Orchestration. Rather the load the whole document into...

It can sometimes be challenging when mapping schemas in BizTalk 2004. One common problem is when the inbound document has one record and the source creates multiple records based on the data inside your single record. The root problem arises because you have nothing to loop around in the inbound document...

I have talked in the past about NACKs . These are great little messages that allow you to receive the status of your sent messages inside your Orchestration. For more information on NACKs, please see my earlier post and sample. The problem I want to point out here occurs if you want to map on the Send...

Updated 8/8/2005: Please note the information below is outdated and I would never recommend mapping messages of this size inside Biztalk 2004. Biztalk 2006 will have support for larger messages by breaking up the message into chunks. More information on large message support can be found on the Performance...

This is a challenge to overcome in BizTalk 2004. It seems that the message never hits the Send Pipeline and as far as I can tell no error is written to HAT. The only place this error is written to is the Event Log. But this is ok if you are using MOM or something else to watch the event log. The messages...