I have follwoing problem.
In destination schema side some element of some base type actually contains
one of derived types (shown in BizTalk mapper in <Equivavalent> section).
When map has links only to one of these derived types, everything is OK. But
when there are links to different derived types within <Equivavalent> (but
logic with Existence functoid controls that only one node produces in
output) BizTalk mapper always set xsi-type attribute to first in list in
Is it some bug and has anybody encountered this issue?