CODEWITHSUNDEEP
xmlbiztalkedibiztalk-pipelines
CreamAbdulJabbar
CreamAbdulJabbar

Reputation: 1

BizTalk pipeline issue? EDI not translating to Web Service

I have tested an EDI file in Visual Studio and the destination schema (Web Service) is populating correctly. However, when I deploy the .dll in production, and I have the send pipeline on my send port set up as Passthrough or XML transmit, the destination schema that is targeted in the map isn't being used. I only get a XML output.

Any ideas on What I'm missing?

Do I need to create a custom pipeline?

Upvotes: 0

Views: 101

Answers (2)

CreamAbdulJabbar
CreamAbdulJabbar

Reputation: 1

There was an EDI Receive on my initial Receive Port that caused this issue. I removed it and added my custom pipeline with an EDI Dissembler and got my file that I wanted. Thanks!

Upvotes: 0

Dijkgraaf
Dijkgraaf

Reputation: 11537

Yes, you need to create a custom pipeline that contains the EDI Assembler or EDI Dissasembler on for your Receive Location (depending on whether you are sending or receiving a EDI).

However you should see the map producing a XML payload that has the the correct schema namespace. If you are not getting that, then your map is not executing either.

Reasons for a map not executing.

  1. The map in not on the send port.
  2. The message being sent to the port does not have a message type on it (usually caused by not having a dissembler on the receive location).
  3. The message being sent to the port has a different namespace or root node (message type) than expected as the source message for the map.

Upvotes: 0

Related Questions