Hello valterwall73,

I was wondering if you figured out the Perform Logic question you posted about 6 months ago?  The reason I'm asking is because I'm trying to create an error log at the end of a VI Job but I don't know the Perform command coding to do this, which might be within the "CREAT_ERRORLOG" you mentioned.

Hi Paul, that's what I'm looking for as well, although my preference would be to preserve a logfile whether there were errors or not.

Natasha Chang - can you assist with this? I'm trying to set this up for an A/P Invoice Import job in a 2022 Advanced system. We have VI jobs set up to run every 5 minutes and we are using batch files to rename the source files and move them to an archive folder. That is working fine, but I would love to get a text file with the Job Log after each time it runs and put that in a LogFile folder. Isn't that something that Perform Logic can do?

Also, just to see if this is possible, couldn't Perform Logic be used to rename and move the source CSV file after the job runs, instead of needing to use batch files?

Thanks

I would ask Alnoor.  He has done a lot with Perform Logic

Rename file script:

https://www.sagecity.com/us/sage100/f/personalization-customization-and-productivity-tools/97518/rename-file-after-vi-import/359306#359306

Thanks BL, I may hit up Alnoor. Might even be worth the price of admission to the vaunted 90 Minds gang.

Thanks Kevin, good old Slade Hornick, that's a blast from the past. I'll give that a shot.

You know VI Job logs are now nicely stored in the Activity Log?  Turn on a VI option, and it links the M4T... (new in v2022... for a couple versions the M4T copies were not-optional).

DSD has (had?) a text file VI job log enhancement, but I expect they might have discontinued it when Sage added this feature.  It only included the first layer of the log (no drill down), where the Activity Log M4T is the full log.

You know VI Job logs are now nicely stored in the Activity Log?  Turn on a VI option, and it links the M4T... (new in v2022... for a couple versions the M4T copies were not-optional).

DSD has (had?) a text file VI job log enhancement, but I expect they might have discontinued it when Sage added this feature.  It only included the first layer of the log (no drill down), where the Activity Log M4T is the full log.

Thanks Kevin,

I knew that, but I never knew there was a VI Options task. Let's see what that cat drags in.

Also, VI1001 is still available from DSD. I have a 10 day demo version for 7.10 which I'm testing as well.