Infor SyteLine creates a .pdf file every time any user runs a report. By default these files are saved on the Utility server in the SyteLine file share (actual path is C:\Program Files (x86)\Infor\SyteLine\Report\OutputFiles). The amount of space these files take can grow quite quickly and it Infor recommends purging of old (stale) reports on a regular basis.

There are a few forms in SyteLine that control where Report Output files are stored, however changes to default values may result in problems such as inability to patch/update the system correctly.

You could modify the TaskMan Path, in the Intranets form. However this would require all contents of the SyteLine share to be migrated to a different location, not just the Output folder.


You could specify the Output Directory in the Report Options form, however this may be a cumbersome task as you may need to configure it per user or per form.


In addition, you could use the Process Defaults form to define values for the Report Output Directory as well as Report Output Obfuscation (typically used in multitenant environments).


With that being said, you are probably still going to want to periodically get rid of stale data regardless of where you choose to store it.

We’ll need to create a batch file that will delete any files older than a specified value (days) in C:\Program Files (x86)\Infor\SyteLine\Report\OutputFiles and all the subfolders. We can use Notepad to type in the command below, then save the document as a .bat file.

forfiles -p “Path” -s -m *.* /D –<Days> /C “cmd /c del @path”

forfiles -p “C:\Program Files (x86)\Infor\SyteLine\Report\OutputFiles” -s -m *.* /D –7 /C “cmd /c del @path”

The example above will delete anything older than 7 days from the default storage location for Report output files.

Next we’ll want to schedule this batch file to run every week or month (frequency depends on how fast your data grows). We can do so by starting the Task Scheduler.


We’ll Create Task, give it a name and description, then navigate to the Actions tab, where we’ll need to select Start a program in the Action drop down.


Use the Browse button, to navigate to the location of your .bat file. In addition you may want to specify the full path to your batch script in the Stat in field (i.e. C:\scripts\).

Lastly you can define when the task will be ran under the Triggers tab.


%d bloggers like this: