BizTalk 2004 File Send Handler Macros Bis

Owen Allen (MS E-Business Technologies) has updated my list of File Send Handler Macros, thanks Owen!

Macro name

Substitute value

%datetime%

Coordinated Universal Time (UTC) date time in the format YYYY-MM-DDThhmmss (for example, 1997-07-12T103508).

%datetime_bts2000%

UTC date time in the format YYYYMMDDhhmmsss, where sss means seconds and milliseconds (for example, 199707121035234 means 1997/07/12, 10:35:23 and 400 milliseconds).

%datetime.tz%

Local date time plus time zone from GMT in the format YYYY-MM-DDThhmmssTZD, (for example, 1997-07-12T103508+800).

%DestinationParty%

Name of the destination party. The value comes from message the context property BTS.DestinationParty.

%DestinationPartyID%

Identifier of the destination party (GUID). The value comes from the message context property BTS.DestinationPartyID.

%DestinationPartyQualifier%

Qualifier of the destination party. The value comes from the message context property BTS.DestinationPartyQualifier.

%MessageID%

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. When substituting this property, the File adapter extracts the file name from the absolute file path stored in the FILE.ReceivedFileName context property. If the context property does not have a value, for example, if message was received on an adapter other than File adapter, then the macro will not be substituted and will remain in the file name as is (for example, C:\Drop\%SourceFileName%).

%SourceParty%

Name of the source party from which the File adapter received the message.

%SourcePartyID%

Identifier of the source party (GUID). The value comes from the message context property BTS.SourcePartyID.

%SourcePartyQualifier%

Qualifier of the source party from which the File adapter received the message.

%time%

UTC time in the format hhmmss.

%time.tz%

Local time plus time zone from GMT in the format hhmmssTZD (for example, 124525+530).

10 Comments

  • how can I assign the value of %SourceFileName% to a variable in an orchestration?

  • Found the answer, place the following in an expression:

    sourceFileName = IncomingMessage(FILE.ReceivedFileName);

  • I need a GUID in the output file name that can also be accessed inside the orchestration.



    I tried using %MessageID% in the output filename and then using BTS.MessageID in the orchestration. But the two GUIDs are not the same. This might be because when a message is sent via SEND port, a copy of the message is being sent and hence it gets a unique, never before seen GUID.



    Any ideas, workarounds ?



    I need this functionality for the following scenario: When i receive a file X, I am trying to create a message that says "file X has been received and renamed to GUID-X".

  • I need a date (i mean a date-macro ;)

  • Great job keep up the good work, and thanks for the help very appreciated.

  • Lucy! Please call me,Lucy! Please call me

  • Lucy! Please call me,Lucy! Please call me

  • Are there any Macros for Receive File Handler for BizTalk 2006

  • Perfect site, i like it!

    tramadol
    [URL=http://idsdev.mccneb.edu/dcarter/_disc2/000001b2.htm]tramadol[/URL]
    http://idsdev.mccneb.edu/dcarter/_disc2/000001b2.htm
    viagra
    [URL=http://idsdev.mccneb.edu/dcarter/_disc2/000001af.htm]viagra[/URL]
    http://idsdev.mccneb.edu/dcarter/_disc2/000001af.htm
    phentermine
    [URL=http://idsdev.mccneb.edu/dcarter/_disc2/000001b1.htm]phentermine[/URL]
    http://idsdev.mccneb.edu/dcarter/_disc2/000001b1.htm
    levitra
    [URL=http://idsdev.mccneb.edu/dcarter/_disc2/000001b3.htm]levitra[/URL]
    http://idsdev.mccneb.edu/dcarter/_disc2/000001b3.htm
    cialis
    [URL=http://idsdev.mccneb.edu/dcarter/_disc2/000001b0.htm]cialis[/URL]
    http://idsdev.mccneb.edu/dcarter/_disc2/000001b0.htm

  • Hi My Name Is ivazqq.

Comments have been disabled for this content.