Loop through multiple records


hi, have mapping problem tried biztalk mapper unable loop through desired output.

if mode or g or e,then map outbound schema claim elements level after header generation. for each inbound message there multiple claimdetails , in each claimdetails there can max of 3 claims. in each of claims(max 3) if found true first records elements goes claim1 , subsequently till claim2 , claim3 record elements.

input: 

<ns0:response xmlns:ns0='http://schemas.response'>
  <ns1:objectresponse xmlns:ns0="http://schemas.objects" xmlns:ns1="http://schemas.claimresponse" recordexist="n" format="ff" id="n" destination="cdd">

<ns1:claimsresponse>
<ns1:batchno>12</ns1:batchno>
<ns1:claimdetails>
<ns1:claims>
<ns1:no>1</ns1:no>
<ns1:member>1</ns1:member>
<ns1:services>
<ns1:mode>e</ns1:mode>
<ns1:state>ma</ns1:state>
<ns1:procedure>d291</ns1:procedure>
</ns1:services>
</ns1:claims>
<ns1:claims>
<ns1:no>2</ns1:no>
<ns1:member>1</ns1:member>
<ns1:services>
<ns1:mode>a</ns1:mode>
<ns1:state>ma</ns1:state>
<ns1:procedure>d291</ns1:procedure>
</ns1:services>
</ns1:claims>
</ns1:claimdetails>

<ns1:claimdetails>
<ns1:no>2</ns1:no>
<ns1:member>6</ns1:member>
<ns1:services>
<ns1:mode>a</ns1:mode>
<ns1:state>ny</ns1:state>
<ns1:procedure>d291</ns1:procedure>
</ns1:services>
</ns1:claimdetails>

<ns1:claimdetails>
<ns1:no>4</ns1:no>
<ns1:member>3</ns1:member>
<ns1:services>
<ns1:mode>g</ns1:mode>
<ns1:state>nh</ns1:state>
<ns1:procedure>d291</ns1:procedure>
</ns1:services>
</ns1:claimdetails>
</ns1:claimsresponse>
</ns1:objectresponse>
</ns0:response>

 output:

<ns0:outbound xmlns:ns0="http://schemas.outbound">
<ns0:header>
<ns0:format>ff</ns0:format>
<ns0:count>3</ns0:count>
<ns0:date>20121007</ns0:date>
<ns0:exists>20121007</ns0:exists>
</ns0:header>
<ns0:claimdetails>
<ns0:claim1>
<ns0:no1>1</ns0:no1>
<ns0:mode1>e</ns0:mode1>
<ns0:state1>ma</ns0:state1>
<ns0:procedure1>d291</ns0:procedure1>
</ns0:claim1>
<ns0:claim2>
<ns0:no1>2</ns0:no1>
<ns0:mode2>a</ns0:mode2>
<ns0:state2>ma</ns0:state2>
<ns0:procedure2>d291</ns0:procedure2>
</ns0:claim2>
</ns0:claimdetails> 
<ns0:claimdetails>
<ns0:claim1>
<ns0:no1>2</ns0:no1>
<ns0:mode1>a</ns0:mode1>
<ns0:state1>ny</ns0:state1>
<ns0:procedure1>d291</ns0:procedure1>
</ns0:claim1>
</ns0:claimdetails>
<ns0:claimdetails>
<ns0:claim1>
<ns0:no1>4</ns0:no1>
<ns0:mode1>g</ns0:mode1>
<ns0:state1>nh</ns0:state1>
<ns0:procedure1>d291</ns0:procedure1>
</ns0:claim1>
</ns0:claimdetails>
</ns0:outbound>

thanks

 

hi,

you can solve problem combining functoids custom xslt. final result should like:


inside scripting functoid (custom xslt), write following code:

<xsl:for-each select="s0:claimsresponse/s0:claimdetails">
<claimdetails>
<claim>
<no1>
<xsl:value-of select="s0:no/text()" /> 
</no1>
<xsl:for-each select="s0:services">
<mode1>
<xsl:value-of select='s0:mode/text()'/>
</mode1>
<state1>
<xsl:value-of select='s0:state/text()'/>
</state1>
<procedure1>
<xsl:value-of select='s0:procedure/text()'/>
</procedure1>
</xsl:for-each>
</claim>
<xsl:for-each select="s0:claims">
<claim>
<no1>
<xsl:value-of select='s0:no/text()'/>
</no1>
<xsl:for-each select="s0:services">
<mode1>
<xsl:value-of select='s0:mode/text()'/>
</mode1>
<state1>
<xsl:value-of select='s0:state/text()'/>
</state1>
<procedure1>
<xsl:value-of select='s0:procedure/text()'/>
</procedure1>
</xsl:for-each>
</claim>
</xsl:for-each>
</claimdetails>
</xsl:for-each>

if want project example, download here: https://www.dropbox.com/s/orc5gwr64gzs5iy/mapchallenge_08-10_2012.zip

hope you,

rui machado

rui machado



BizTalk Server  >  BizTalk Server General



Comments

Post a Comment

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

having same error microsoft.azure.documents.documentclientexception: message: {"errors":["owner resource not exist"]} , scenario. when deployed webapp azure , try document docdb throws error. docdb exists in azure , contains document looking for. weird local machine(running vs) works fine. i'm using same settings in azure , local. have , idea this. thanks Microsoft Azure  >  Azure Cosmos DB
Read more

BizTalk Server 2013 Azure VM Log Shipping and HA for hosts

hi , background: for our customer, having a  2 biztalk , 1 sql setup of environment. [biztalk server 2013 azure vms provisioned azure gallery, sql server 2012 azure vm ]. in current configuration, there no high availability or disaster recovery plan set. want implement dr , possibly ha configuration on these servers. i have few questions regarding same. please let me know thoughts on same. currently writing log files (log shipping files) mounted/attached drive same sql server. how move these log files across secondary site since shared storage not supported. in case of sql server crash, losing log files since reside on same server. please share options on how can move these periodically between datacenters. for hosts pop3, ftp need host clustering (which requires biztalk machines present on windows cluster traditionally), please let know how achieve in azure scenario thanks , regards, ujjwal devarapalli -ujjwal you can refer article, issue azure vm lo...
Read more

How to send non-standard Content-Type header ?

hello, my custom client developed send custom content-type header "xyz" (with out "/"). message gone in lcs 2005. after have upgrade lcs 2005 ocs 2007 r2 in test environment. custom client not able send same custom content-type in ocs 2007 r2 used possible send in lcs 2005. below cut ocs 2007 r2 accessedge log file. tl_warn(tf_component) [0]0f68.0bb4::11/08/2010-06:02:51.546.00000de7 (sipstack,ccontenttypeheader::parse:contenttypeheader.cpp(118))( 00000000036249f0 ) exit - media-type syntax error in getting "/" tl_error(tf_component) [0]0f68.0bb4::11/08/2010-06:02:51.546.00000de8 (sipstack,csipmessage::parseallheaders:sipmessage.cpp(6408))( 0000000003566a50 ) exit. failed while parsing header. tl_error(tf_component) [0]0f68.0bb4::11/08/2010-06:02:51.546.00000de9 (sipstack,csiprequest::validateinboundheaders:siprequest.cpp(1391))( 0000000003566a50 ) exit - failed while parsing header. returned 0xc3e93f51(sipproxy_e_invalid_content_type_header)...
Read more