File path pattern tokens

When you specify the file path pattern for a File Data Set, you can use the following file path pattern tokens:

Date / time token

The date / time token is represented by %{FORMAT} where FORMAT is any date time format accepted by java.time.format.DateTimeFormatter with the exception of timezone specifications "zzzz", "V", "X", "x", "Z", and "O".

The date / time token matches file names that contain a date and time in the specified format.

For new files, the date time token generates the current date in the specified format.

Wildcard token

The wildcard token is represented by the * (asterisk) character.

For existing files, the wildcard token matches any non-empty string.

For new files, it generates a unique ID to guarantee file name uniqueness.

Implicit token

If the wildcard token is not present, the implicit token is added to the pattern to guarantee file name uniqueness.

The token is added at the end of file name, right before extension.

An implicit token matches the file names that do not contain a token value, or contain a value consisting of the - (hyphen) character followed by any string.

New file names are generated with - (hyphen), followed by a string that guarantees file name uniqueness.

A new file name without a token value is never generated, for example, assuming the path file.json, a file called file.json is never generated.

File name uniqueness when generating files

All files that the system generates in a file repository by using a File Data Set, include a unique ID in the file name. This ID is a string that guarantees the uniqueness of the file names. For example, if the file name pattern for a File Data Set is file.json, the system generates files names with unique IDs after a hyphen (-) and before the file extension:

• file-vlmmssaprdnd7421164395985556020230321.csv
• file-vlmmssaprdnd7421164395986666420230321.csv
• file-vlmmssaprdnd7421164395983234420230321.csv

If the file name pattern includes a wildcard character (*), for example, file*.json, the system generates file names by replacing the wildcard character with a unique ID:

• filevlmmssaprdnd7421164395985556020230321.csv
• filevlmmssaprdnd7421164395986666420230321.csv
• filevlmmssaprdnd7421164395983234420230321.csv

The system does not generate any file names without a unique ID. For example, file.json is not a valid file name for new files and is never generated.

Examples of file path patterns

To better understand the different tokens, refer to the examples provided in the following table:

Examples of file path patterns