Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
stevelord
Specialist
Specialist

How to make nprinting outputs overwrite?

Hi, is there a way to make nprinting outputs overwrite?  I thought if I left the timestamp off the filename,and ran the job a second time, it would overwrite the files it created on the first run.  Am I overlooking a checkbox or something somewhere?  Thanks!

(Simple workaround would be delete/archive the old batch of outputs, but looking for 0 maintenance and overwrite would help that.)

1 Solution

Accepted Solutions
alexpanjhc
Specialist
Specialist

Do you run it manually or it runs off a schedule? If it is scheduled job, it will not created an output in the local directory(your computer). Only if you run manually, your local (not server) directory will have that output available after successfully run.

Maybe that is where you are having issues?

View solution in original post

6 Replies
alexpanjhc
Specialist
Specialist

I'm not sure why it is not working for you.

I have a task and I save the output in the local directory. Every time I re-run it, it overwrites.

I am curious how the name can be different from the first time?

stevelord
Specialist
Specialist
Author

Thanks for confirming that's how it should work.  I will check and see if something else is the issue.  I will likely apply correct answer to your post when I confirm and know what actually happened.

The job ran its course and finished successfully with no errors according to the log, and the log indicated files were being copied to the correct folder.  But when I went to that folder, it still had the files with last modified date of the previous day and they were unchanged.  (I had adjusted the qlikview expressions to make a placeholder if the expression came to 0, so the rows would remain on the nprinting output that pulled those numbers, but I didn't see the new versions of the nprinting outputs in the folder after I ran it again.)

avinashelite

Strange !! If your having the same name for the output files then has to overwritten the old files ..I have never faced this sort of issue. Please check again and if face any issue please let us know.

alexpanjhc
Specialist
Specialist

Do you run it manually or it runs off a schedule? If it is scheduled job, it will not created an output in the local directory(your computer). Only if you run manually, your local (not server) directory will have that output available after successfully run.

Maybe that is where you are having issues?

stevelord
Specialist
Specialist
Author

Thanks, I am running it manually for now.  I developed it on my local desktop, and it outputs to network drive folders like S:\nprinting\outputs\.  When I moved the nsq up to the server environment, I switched out the s:\ with the ip reference for the drives like 12.345.67.8\drivename\nprinting\outputs\ and ran it again.  My qlikview named license is on both machines, and I had an nprinting designer license for myself on each machine to be able to run it manually on both machines while developing.  (The server environment would ultimately host the scheduled nprinting jobs once I'm done making/testing them.)  It ran okay from the server environment and finished successfully like it did from my local machine, just the files had not overwritten.

So, I will test the scenarios of having it scheduled and run by nprinting server service from the server environment, to see if that overwrites as intended.  And I will also test to see if running manually from my local machine overwrites as intended while I'm testing.   And maybe running it manually from the server environment was the scenario that doesn't overwrite, as you indicated.

stevelord
Specialist
Specialist
Author

It overwrote successfully when I ran manually from my local desktop, so that's good.

It did not overwrite when I ran manually from the server environment, which was the problem scenario that brought me here..

I have not tested a scheduled run from the server environment to see if that overwrites yet, but confident it will for me if it did for you.  (I'm going to run manually while we vet the next couple of monthly iterations, and effort of clearing a folder if I had to for the scheduled run would be negligible.)