When an AutoTask is saved, any path to a file outside IFP is stored as relative to the Public Documents or Source Files path, if possible. E.g. if importing from a file named example.xlsx in the Source Files folder, the AutoTask will be saved referring to [Source Files]\example.xlsx
Changing Database Paths
Changing the Public Documents and Source Files paths will result in different default folders. For AutoTasks that use the default folders in their paths to external files, this means they will export to the new default folder, or expect import files to be in the new default folder. When you change either path, IFP will check if any Import AutoTasks use that path. If any do, you will be asked if you are moving your source files to the new path:
If you are moving your source files, then answer Yes and IFP will leave the AutoTask path settings as they are. In the example screen above, IFP would expect the file that was at
to now be at
If you are not moving your source files, then answer No. IFP will then put the full old path into the AutoTasks, so that they still work. E.g. an AutoTask referring to
will be changed to refer to
Simplifying AutoTask Paths
If you have AutoTasks that have a full path to a file (e.g. \\Server\Path\To\Shared\Source Files\example.xlsx, rather than [Source Files]\example.xlsx), then changing where you keep your Source Files or Public Documents would mean changing each AutoTask individually.
IFP can automatically change Import or Export AutoTask path to the short version: clicking Simplify AutoTask Paths… on the Database Properties Advanced Settings tab will do that for all relevant AutoTasks:
If you have any questions over the impact of changing your database paths, whether to answer Yes or No to Are you moving your source files or about simplifying paths, please contact support.
Please sign in to leave a comment.