In this article
All export tasks will generate files with unique names in the following format: <projectid>_<userid>_<taskid>.<extension>. The "Override file name" functionality, available as a checkbox on all export dialogs, allows you to override this system-generated name.
Note: The '_^PROJECTID^_' part of the name will be replaced by the real survey id during the export. Default is ^PROJECTID^_^USERID^_^TASKID^ (if Date Filter is used, then ^START^ and ^END^ will also be included). ^PROJECTID^ is only "required" when executing a rule; it is not "required" when running an export using the Export GUI.
You can add dynamic values to the overriding file name such that the file name becomes more intuitive and it is easier to see what the file contains. The following dynamic values can be added to the file name:
- ^PROJECTID^ - the project id for the current project
- ^TASKID^ - the task id of the current export task
- ^USERID^ - the user id of the current user
- ^NOW^ - the current date (yyyyMMdd)
- ^YEAR^ - the current year
- ^MONTH^ - the current month with no leading zero
- ^MONTH2^ - the current month with leading zero when appropriate
- ^DAY^ - the current day with no leading zero
- ^DAY2^ - the current day with leading zero when appropriate
- ^HOUR^ - the current hour with no leading zero
- ^HOUR2^ - the current hour with leading zero when appropriate
- ^MINUTE^- the current minute with no leading zero
- ^MINUTE2^ - the current minute with leading zero when appropriate
- ^START^ - the start date (yyyyMMdd) in the date filter
- ^STARTYEAR^ - the year in the date filter start date
- ^STARTMONTH^ - the month in the date filter start date with no leading zero
- ^STARTMONTH2^ - the month in the date filter start date with leading zero when appropriate
- ^STARTDAY^ - the day in the date filter start date with no leading zero
- ^STARTDAY2^ - the day in the date filter start date with leading zero when appropriate
- ^END^ - the end date (yyyyMMdd) in the date filter
- ^ENDYEAR^ - the year in the date filter end date
- ^ENDMONTH^ - the month in the date filter end date with no leading zero
- ^ENDMONTH2^ - the month in the date filter end date with leading zero when appropriate
- ^ENDDAY^ - the day in the date filter end date with no leading zero
- ^ENDDAY2^ - the day in the date filter end date with leading zero when appropriate
For example, using the following text and dynamic values: "Monthly_Export_^MONTH^_^YEAR^_^PROJECTID^_^TASKID^_^USERID^" will give the file name "Monthly_Export_2_2020_p99999999_0990909_johndoe.zip".
And "Monthly_Export_^MONTH2^_^YEAR^_^PROJECTID^_^TASKID^_^USERID^" will give the file name "Monthly_Export_02_2020_p99999999_0990909_johndoe.zip".
You can add different dynamic values for each export type.
Note that when exporting Survey Data to the FTP server in Survey Data > Exports or Data Processing rules, the Override Filename option accepts relative paths, as for example “..\..\myftpfile_in_another_folder.txt”. In this case the file will not be stored in the default folder (“ProjectsData\p123123” or “RulesData\RuleN”), but rather directly under the (Company) Download folder.
Note: If you are using a recurring rule and the rule does not contain ^TASKID^, depending on the dynamic values used the output file may be overwritten each time the task is run.