When setting up a File Writer or an Azure File Writer, specify the name of the file to create. The assist edit on the File name field opens a list of predefined macros you can use in naming the file. These macros replace at run time with actual values.
Macros
This table shows the macros you can use on file writer endpoints":
Token | Description |
|---|---|
$(MessageNumber) | A unique message number linked to the message. |
$(Month) | Current month. |
$(DayOfMonth) | Day ordinal of the current month. |
$(Year) | Current year. |
$(Hours) | Current hour. |
$(Minutes) | Current minute. |
Table field value from the incoming record. | |
$(FullOriginalFileName) | Original file name including the extension. |
$(OriginalFilename) | Original file name excluding the extension. |
$(OriginalFilenameExtension) | Original file name extension, without the dot; for example, |
TableField()
The File name formats page lets you include field values from the incoming record. Replace
Scenario:
Record: Table Sales Header with fields Document Type, No., Sell-To Customer Name.
Connection: Timer Event > XML Generator > Splitter > Azure File Writer with file name set to Order_$(TableField(
Setting the file name to Order_$(TableField(No.)).xml includes the sales order number in the file name; for example, Order_SO01234.xml.
Solution Center setup
If a macro cannot translate at run time, the default value applies. This format can conflict with Azure Storage file name restrictions.
To prevent message failures due to curly brackets, enable the Macros with parentheses flag in Solution Center Setup. When enabled, macros use parentheses () instead of curly brackets {}. This is a global setting.
