ETA - I changed it to a .bat file and got it to work on my local v2021.3 Standard but not on the client's v2022.2 Premium 64 bit.  The .bat runs fine outside of Sage, just not from the perform command.  No error message now, it just doesn't seem like it's firing.

I've used the full UNC in the .bat file since the users are on RDS.

With the runtime version of ProvideX you must execute your statements. Try execute to run the perform statement. You can run ProvideX code in text form if it is called or performed.

Thanks, but I don't understand what you mean.  Isn't that what the perform command does - executes the statement?  It runs in my v2021 standard but not in v2022 Premium.

With Premium the perform script will run in the security context of the Sage service, not the workstation (which is how the perform script would work for Standard).  Make sure the Sage service is running under a domain login (with appropriate permissions) and not something like LOCAL SERVICE, which won't be able to use a UNC path.

Thanks, Kevin.  I was afraid it was permissions.  The user running the service is a domain admin account and I'm testing on the server, not an RDS workstation.  I will check to make sure the user running the service did not get changed.  

If you just want to rename a source file after a VI job, try this (instead of a VBScript):

https://www.sagecity.com/us/sage100/f/technical-and-installation-discussions/170634/importing-sales-orders-premium-version/436950#436950

Thanks, Kevin.  I need it to run on Completion so that it doesn't get moved if the job doesn't complete.  I think I need to keep it in the Perform Logic and not windows task scheduler for that validation to happen.

This is for running as Perform, just not using VBScript.

I really appreciate the help, Kevin.  Maybe a stupid question, but why would that be treated differently than the .bat file I'm trying to run? What is a .PL?

That is written in the same language as Sage 100.  It isn't running an external program.