One of my colleagues struck a problem trying to map to a rather nasty schema shown on the right below;
The user element has an attribute of business-partner-no and there is a child element of the same name. No matter what you do if you try to drag a link to the child element called business-partner-no the link always gets connected to the attribute of the same name.
I am writing about this because I have just spent the morning changing the map to custom XSLT to get around the problem.
Is this by design or is this a bug with the BizTalk 2010 mapper? Does this occur with the mappers in previous versions of BizTalk?