More tricks on handling hierarchical XML in the BRE…these techniques need to be better documented on MSDN!
Oops, this must be the longest and worst blog post title you have ever seen. Let’s quickly make clear what I mean:
Recently I needed to update multiple elements using a single rule in the Business Rule Engine (BRE). To most BizTalkers this is nothing special. The thing that complicated this particular scenario was that the elements to update where in different hierarchical levels within the xml instance and thus had different parent nodes.
See the following XML and corresponding XSD instance for an example of this scenario:
<ns0:Customer xmlns:ns0=“http://Samples.BRE.Customer“>
<Name>John</Name>
<Discount>10</Discount>
<Accounts>
<Account>
<ID>12</ID>
<Discount>10</Discount>
</Account>
<SubAccounts>
<SubAccount>
View original post 1,068 more words