There appears to be an issue when using an automation variable - specifically a text variable - with an Export Template in at least one scenario.
I created an automation and created a variable used to hold an output file name (to make it easily changeable later, if needed), and then I created an Export Template because I needed data output in a specific format (tab delimited, all data quoted).
I used the automation variable (#FileName# set to VENDOR_FILE_#Date#A.txt), in the output options as seen below:
However, upon executing the template, the file created is named 'VENDOR_FILE_12312015A.txt'.txt :
I was able to work around this by changing the Export Template output options to:
But I would like to avoid hard-coding the file name, since in order to update it you have to edit the export template, instead of just opening the automation and updating a variable.
As I see it, there are two issues here
- The export template adding the extraneous single quotes/tick marks around the file name, if the filename itself is a variable - though having a variable in the filename doesn't appear to be an issue, oddly enough.
- The export template forcibly sets the file extension to .txt no matter what. The export template should be agnostic as to the output file extension, leaving it up to the automation developer to determine.