FILE.ReceivedFileName and EDI

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › FILE.ReceivedFileName and EDI

Viewing 1 reply thread
  • Author
    Posts
    • September 8, 2008 at 7:42 AM #20630
      community-content

        In BizTalk 2006 R1 you cannot utilize the FILE.ReceivedFileName value when processing EDI files. Can this value be utilitized now in R2?

      • September 8, 2008 at 8:12 AM #20631
        community-content

          Greg,

          Are you using the file adapter to receive the files?  FILE.ReceivedFileName is a file adapter specific context property, so the file adapter is required to set it.  I don’t think this functionality has changed between R1 and R2.

          Regards,

          • September 8, 2008 at 10:17 AM #20634
            community-content

              Ya, we receive EDI files and unfortunately we need to know what the filename is. This has been a bit of a pain in R1 and I was hoping R2 with it’s changes to the way EDI files are process would allow me to get this value.

               

              Are EDI files picked up using a file adapter in R2? I haven’t looked that deeply into R2 yet, but I have noticed that the EDI processing is drastically different.

              • September 8, 2008 at 10:33 AM #20636
                community-content

                  I haven’t done any EDI work, but I think the most common method is to send the files over HTTP.  It seems strange that the file adapter would behave differently for you depending on what type of files you are processing.  It seems like the file adapter would set the same context properties no matter what kind of files it is processing.  Does MSFT know about this issue?

                  • September 8, 2008 at 10:36 AM #20637
                    community-content

                      EDI file processing in R1 is strange because it uses a special File Adapater, not the standard File adapter. This special adapter didn’t populate/promote the Recevied File Name or the %Filename% macro. Because of the changes to EDI processing in R2 I was hoping that this would now be possible.

                      • September 29, 2008 at 5:16 AM #20863
                        community-content

                          FILE.ReceivedFileName is now promoted by BizTalk for EDI files. EDI Processing in R2 is much cleaner than R1 and if you do any heavy EDI work R2 is the way to go!

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