As the example below shows, there are three (3) sub-directories named and created by the File Connection - File, Audit and Error.

The File Connection object class TFloFileCon can be used to interact with the File Connection during a mapping process, to provide access to properties of the File Connection/s so they can be altered for this specific Map.

You can access TFloFileCon by referencing Source.FileCon or Dest.FileCon as variables, where Source and Dest are pointers to the source and destination data definitions of the Map.

At Action level, the File Connection for an Action Step can be referenced in the following form, where [i] is the zero-based index of the Action Step -

Action.Actions[i].Source.Source.FileCon (for source data definitions)

Action.Actions[i].Dest.Source.FileCon (for destination data definitions)

Among other things, the following tasks can be achieved by working with TFloFileCon -

  • Changing the name of an outbound file - for fine-grained control over the name of the outbound file you can edit the Dest.FileCon.FileName property.

  • Reading the name of an inbound file - you might want to store the name of the inbound file as you are processing it. You can read the name from Source.FileCon.CurrentFileName.

Declaration: Source.FileCon : TFloFileCon

Dest.FileCon : TFloFileCon