We use Perform Logic to rename the input file (adding date / time stamp) so it won't be overwritten when a new file is put in place, but you still have it for reference.

! Rename the source file (originally created by Slade Hornick)
!
! Put the Import file in something more manageable
f$=ImportFileName$
!
! Close the source file, before trying to move it
close (1,err=*next)
!
! Create a name for the new file
f_new$=f$+"-"+dte(0:"%Y%Mz%Dz-%Hz%mz%sz")+".imported"
!f_new$=f_dir$+f_file$+".old"
rename f$, f_new$
exit

Thank you. That would be a great option. Do you think creating a windows batch file to run a VI job outside of Sage is the most efficient way to run the same VI job multiple times a day? Or is windows task scheduler better?

Create a batch file, then use Windows Task Scheduler to run it.  No mapped drives... and the Sage service account needs appropriate permissions.

Since you are using Premium, be sure to add the changes to the Sage service, as described in the Sage KB.

Running imports without this (in MAS90 mode) can cause problems.

Kevin, sorry for the reply on this old thread.  Does this require a restart of the Sage service after adding these parameters in the app server config?  Thanks!

Yes.

....and UNC to the Home directory for the Start-in as opposed to local drive reference?

That path is how the service finds the Sage files... a local path is fine.