What you need to do is have different file mask for each receive location. That will make the URI's unique. For example if all the files have a pattern off PCK00001.xml, PCK0002.xml etc. you can have one port looking for P*.xml, a second PC*.xml and the third as PCK*.xml. That would be enough to make BizTalk think the URI's are unique.
Beware of the ampersand when using XML. by Brian Schaffner in Developer on October 29, 2001, 12:00 AM PST An XML document is a great way to represent information. But some characters, such as the
How to Filter by Filename by Mask in BizTalk. August 11, 2017. * and allow the SendPort to do a subscription when the file does NOT contain a given mask. * For example, in BillTrust, there was need to write file to disk if filename * contains 'Export' but not '*.txt'.
The BizTalk Messaging Engine always validates the file name and file mask properties at design time by using the items previously listed. In addition, the File adapter validates the file name and file mask properties at run time if the adapter sends the message on a dynamic port.
The audience didn’t know whether to laugh, cry or cringe at the 8th Annual Crunchies Awards Thursday night, at San Francisco’s Davies Symphony Hall.
Only one file mask or file name can be specified per receive location or send port. See MSDN: Restrictions on the File Mask and File Name Properties. However, you can use the File Adapter SDK Sample and build your own Adapter to use a regular expression as described in this blogpost.
Globally unique identifier GUID of the message in BizTalk Server. The value comes directly from the message context property BTS.MessageID. %SourceFileName% Name of the file from where the File adapter read the message. The file name includes extension and excludes the file path, for example, foo.xml.