Problem with Biztalk mapper
Web Server forum
Back To The Forum Home!Search!Private Messaging System

Web Server Talk Web Server Talk > Web Servers reviews > BizTalk Server > BizTalk Server Orchestration > Problem with Biztalk mapper




  Last Thread   Next Thread Next
  Show Printable Version Email this Page Subscribe to this Thread      Post New Thread    Post A Reply      

    Problem with Biztalk mapper  
Amit


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
04-21-04 04:35 AM

I had mapping scenario in where I am having 3 input xml file and 1 output xm
l file, which I can easily specify in the mapping component in the orchestra
tion. The problem is when it opens the mapper. It shows that it had 3 input 
xml’s but only shows fiel
ds of first input xml and the other two as empty. When I go back to the orch
estration and try to click on the transform component it says that the signa
ture of the map file has changed, some arguments that you specify may not be
 valid. I believe it is pos
sible to have multiple input file and one output file, Am I missing somethin
g?.

Thanks
Amit






[ Post a follow-up to this message ]



    RE: Problem with Biztalk mapper  
Tan Bao Nguyen


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
07-09-04 08:33 PM

Is the issue resolved?

Regards,
Tan Nguyen
Microsoft BizTalk Server

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------[vbcol=seagreen] 
xml file, which I can easily specify in the mapping component in the
orchestration. The problem is when it opens the mapper. It shows that it
had 3 input xml’s but only shows fields of first input xml and the other
two as empty. When I go back to the orchestration and try to click on the
transform component it says that the signature of the map file has changed,
some arguments that you specify may not be valid. I believe it is possible
to have multiple input file and one output file, Am I missing something?.

Thanks
Amit
[vbcol=seagreen] 






[ Post a follow-up to this message ]



    RE: Problem with Biztalk mapper  
Tan Bao Nguyen


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
07-09-04 08:33 PM

Amit,

Did you change the schemas or namespaces afterward?

Regards,
Tan Nguyen
Microsoft BizTalk Server

This posting is privided "AS IS" with no warranties, and confers no rights.

--------------------[vbcol=seagreen] 
xml file, which I can easily specify in the mapping component in the
orchestration. The problem is when it opens the mapper. It shows that it
had 3 input xml’s but only shows fields of first input xml and the other
two as empty. When I go back to the orchestration and try to click on the
transform component it says that the signature of the map file has changed,
some arguments that you specify may not be valid. I believe it is possible
to have multiple input file and one output file, Am I missing something?.

Thanks
Amit
[vbcol=seagreen] 






[ Post a follow-up to this message ]



JonathanWu is offline     Re: RE: Problem with Biztalk mapper  
JonathanWu


View Ip Address Report This Message To A Moderator Edit/Delete Message


Click Here to See the Profile for JonathanWu Click here to Send JonathanWu a Private Message Find more posts by JonathanWu Add JonathanWu to your buddy list
 
11-17-04 06:17 PM

I am pretty sure the problem you encountered is due to the namespace#rootEle
ment collision. If you are using the same namespace for those 3 inbound xml 
documents and these documents also have the same root element, you will run 
into this problem exactly as you described. You need to make sure the defini
tion of your xml namespaces will always allow BizTalk to derive a unique typ
e. The simple solution to your problem could be: 

1. use a dinstinct namespace name for each inbound document schmea; or
2. use a distinct root element name in each schema. 

One common scenario you will run into this problem is when you use the schemas generate
d by the SQL Adapters invoking the stored procedures. If you let the stored procedure t
o return "FOR XML RAW" and you have the same namespaces for these stored procedures gen
erated schemas, then BizTalk mapper will not be able to import the rest of schemas sinc
e there's a type collision after importing the first schema. You will have these collis
ions if you define your namespace to be: http://mynamespace. 

InputMessagePart_0: http://mynamespace#row
InputMessagePart_1: http://mynamespace#row
InputMessagePart_2: http://mynamespace#row


Go to my blog to find more information: 
http://biztalkshow.blogspot.com

Jonathan Wu


Last edited by JonathanWu on 11-17-04 at 06:32 PM



[ Post a follow-up to this message ]



    Sponsored Links  




 





   All times are GMT. The time now is 01:20 AM.      Post New Thread    Post A Reply      
  Last Thread   Next Thread Next


Most Popular forums 

Forum Jump:
Rate This Thread:

Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
 
Medical and Health forum | Computer Games Reviews | Graphics design forum

Back To The Top
Home | Usercp | Faq | Register