We have two incoming messages to an Orchestration. Data from both of these messages are to be used to construct another message which will be sent to an external system.
Of the two incoming messages, one is fairly simple with a mix of records and elements, the other is complex, built up of a number of extended types from schema dictionaries.
Using Windows XP SP2 workstations with .Net 2003, BizTalk developer tools etc installed (all have .Net 1.1 SP 1, BizTalk 2004 SP1 and one has the BizTalk rollup), the complex schema does not display properly in the source pane of the mapping tool when this is part of a two-message input via the Transform shape.
What seems to be happening is that any element declared on the base data type in the schema is missing, while properties on the extended type are OK. If the map is changed to only input the one, complex schema, everything displays correctly.
Also, a colleague running Windows 2003 Server with Visual Studio and BizTalk has tried this, and on that environment, the complex schema displays correctly when part of a two message mapping source.
It would appear as if the Server 2003 environment has a BizTalk, Studio or .Net Framework patch that we do not have on the XP environments, however all that we have examined suggests that we do in fact have all the same service pack, framework patch levels etc.
The following screen captures illustrate what we are seeing when we have the two message input on XP:
[img:158574d987]http://www.eveleigh.f9.co.uk/images2/fig1.jpg[/img:158574d987]
The \”FMAApplication\” record shows a single sequence containing four records, the first of which contains two fields. What it should look like (if the map is changed to have just the complex schema in place) is as follows:
[img:158574d987]http://www.eveleigh.f9.co.uk/images2/fig2.jpg[/img:158574d987]
As you can see, there are far more sequence groups, records and fields in the full Schema!
For info, the transformation shape in the Orchestration is being configured as follows:
Source transform:
[img:158574d987]http://www.eveleigh.f9.co.uk/images2/fig3.jpg[/img:158574d987]
Destination transform:
[img:158574d987]http://www.eveleigh.f9.co.uk/images2/fig4.jpg[/img:158574d987]
Any thoughts or suggestions as to what fixes/patches we may be missing, or configuration we may have missed to resolve this would be really appreciated.