File Copy Feature Representation

In addition to the generic FME feature attributes that FME Workbench adds to all features (see About Feature Type Attributes), this format also adds format-specific attributes (Format Attributes).

Attribute Name	Contents
filecopy_source_dataset	The source location from which to copy files. This is expected to be an existing file or folder complete with either relative, absolute, or UNC paths. Relative paths are with respect to the workspace folder. Note that backslashes will have to be escaped but forward slashes are also acceptable. Basic glob or wildcard patterns are also supported. Example values might include: ../sourcedir/myfile.txt c:/temp/mydir/ \\\\mycomputer\\mydir\\ c:/mydir/.mov c:/mydir/myfile.r?? Range: valid path and filename or folder
filecopy_dest_dataset	The destination folder for the output files. If this value is not specified the destination dataset will be the destination for all copy or move operations requested from all input features routed to the writer. This attribute allows each input feature defining a copy or move operation to specify a new destination folder for the source data already specified on the feature. This format attribute can be formatted as either a relative, absolute or UNC path and must be specified using forward slashes (c:/temp/) or escaped backslashes (c:\\temp\\). If specified as an absolute or UNC path, it will replace the destination dataset entirely; however, if it is a relative path, it will be appended to the destination folder. This is expected to be a folder name and can be used in conjunction with the filecopy_dest_filename. If the folder does not exist, it will be created. Example values might include: ../destdir/ c:/temp/mydir/ \\\\mycomputer\\mydir\\ Range: a valid folder path
filecopy_dest_ filename	The new name for the output file instead of using the source file name. This is only effective if the filecopy_source_dataset attribute contains the path to an existing file, not a folder or glob pattern. Note that folder renaming when copying and moving is already implicitly supported when the destination dataset is specified. This is expected to be a file name with an optional file extension. If the file exists, the OVERWRITE_FILE directive will be consulted to determine behavior. Example values might include: myfile.txt noextensionfile Range: a valid filename

Attribute Name

Contents

filecopy_source_dataset

The source location from which to copy files. This is expected to be an existing file or folder complete with either relative, absolute, or UNC paths. Relative paths are with respect to the workspace folder.

Note that backslashes will have to be escaped but forward slashes are also acceptable. Basic glob or wildcard patterns are also supported.

Example values might include:

../sourcedir/myfile.txt

c:/temp/mydir/

\\\\mycomputer\\mydir\\

c:/mydir/*.mov

c:/mydir/myfile*.r??

Range: valid path and filename or folder

filecopy_dest_dataset

The destination folder for the output files. If this value is not specified the destination dataset will be the destination for all copy or move operations requested from all input features routed to the writer. This attribute allows each input feature defining a copy or move operation to specify a new destination folder for the source data already specified on the feature.

This format attribute can be formatted as either a relative, absolute or UNC path and must be specified using forward slashes (c:/temp/) or escaped backslashes (c:\\temp\\). If specified as an absolute or UNC path, it will replace the destination dataset entirely; however, if it is a relative path, it will be appended to the destination folder.

This is expected to be a folder name and can be used in conjunction with the filecopy_dest_filename. If the folder does not exist, it will be created.

Example values might include:

../destdir/

c:/temp/mydir/

\\\\mycomputer\\mydir\\

Range: a valid folder path

filecopy_dest_ filename

The new name for the output file instead of using the source file name. This is only effective if the filecopy_source_dataset attribute contains the path to an existing file, not a folder or glob pattern. Note that folder renaming when copying and moving is already implicitly supported when the destination dataset is specified.

This is expected to be a file name with an optional file extension. If the file exists, the OVERWRITE_FILE directive will be consulted to determine behavior. Example values might include:

myfile.txt

noextensionfile

Range: a valid filename