I see their is documentation on how to send an output to a GoogleDrive. I am wondering is there a way to send a report from NPrinting to OneDrive. If there is can someone share a link with me.
Share your folder with the user who you login as on the server, when shared, you then need to go to sharepoint and sync that folder on the qlikview server. Instructions here
David - one generic approach with all of the cloud based storage options is to write NPrinting output files locally to the appropriate 'synced' folder and simply let the desktop cloud app or native capabilities of the cloud sync keep the content replicated between the local NPrinting Server and the Cloud site. There are valid reasons to keep a copy of the report both on-prem and in the cloud. It's a simple approach that leverages the vendors own technology. To let NPrinting drop a file to a local folder is no different than a user dragging the file in.
For One Drive their documentation says:
To upload files to OneDrive automatically, just copy or move the files to your OneDrive folder using File Explorer, or save them in your OneDrive folder from a program. Files you upload this way can be up to 10 GB in size. If you installed the OneDrive app on other computers, the files will automatically be added to the OneDrive folders on them, too.
I am trying to use this exact method you suggested, however my issue is that the folder path is related to the user who is logged in e.g. C:\Users\\
The problem with this is i use a particular user for testing e.g. NPRINT_TEST and another user for the actual live environment NPRINT_PRD. If I hardcode the path to save the report in Nprinting nsq then I have to remember to change it every time I want to TEST or promote to Production.
Do you know of a way around this?
My thanks in advance for any suggestions
You mentioned an .nsq so I suppose you are working with QlikView NPrinting 16. In this case QlikView NPrinting 16 supports environment variable. So you could use variables in the paths and simply change a variable when moving the project to the production environment.
That will reduce maintenance to only a single manual update, but ideally I was looking for a way that the variable could be derived depending on which environment it's in e.g. pickup from a text file on the environment declaring the variable value. I cannot seem to do this last step, no logic can be applied to the environmental variables it appears.
Anyway, it reduces the workload anyway to a single maintenance which helps massively
So for anyone interested in a full resolution to this issue, there is actually a much simpler solution. What I was not aware of is that this One Drive folder on the local machine is simply just another standard folder with security permissions, so if you simply give read/write permissions to Test User of the Production User's folder then it does not matter if while running as test user you save to production user's folder, it allows that.
So, to be clear, no variables required for this in the end, just setup folder permissions.