Alternative to FILE.ReceivedFileName when using EDI Adapter

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Alternative to FILE.ReceivedFileName when using EDI Adapter

Viewing 1 reply thread
  • Author
    Posts
    • #18229

      Does anyone have an alternative to FILE.ReceivedFileName when using an EDI Adapter? FILE.ReceivedFileName is not populated/promoted by the Base EDI adapter.

      I've been told that the %SourceFileName% macro doesn't work either. I really need the filename and I don't want to have to use a GUID or something like that.
       

    • #18230

      Possible Solution: I have a round-about way of solving this conundrum…

      Have a FILE adapter configured to pickup the EDI file at location B, write a message EDI File Context message to the message box, then write the EDI file to Folder B. EDI File Adapter picks up EDI files from folder B and has a parallel receive port that subscribes to EDI File Context messages. Only when the Orchestration has received the EDI Message and the corresponding EDI File Context message will the orchestration continue.

      This is very round-about and I find it very stupid that the Received File Name is not included in the original BizTalk 2006 Release. If anyone can think of a reason that this wouldn't work, let me know…let me know if you think it will work to 😉

Viewing 1 reply thread
  • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.