You should use Environment Variables in your QlikView NPrinting projects. This way you only need to change the value of the Environment Variables when you deploy to Production. Take a look at this document: How to Use Environment Variables
HTH - Daniel.
Daniel, thanks for prompt reply.
I just wonder why NPrinting did not use system's environment variables or Qlikview include files feature. In this way we don't need to make any changes in NPrinting while promoting these changes. We just need to define different paths in different environments only once and the whole process would work without any issue.
Taking your scenario you simply need one environment variable. Example:
Use that everywhere in your project (NSQ). E.g., %evProjectRoot%\SourceDocs\5.NPrintingQlik\1.Application\NPrintingQlik.qvw
Since you already have the required environment in place and are happy with it, when deploying from Dev. to Prod. you need to make just one single change to the value of the environment variable in the NSQ:
evProjectRoot = \\FileServer\qv-prod
In my opinion this is a great feature making the deployment process very simple. You don't have to agree
Our environment might not be typical as our data is static and updated on a monthly basis. In addition to what Daniel says, we typically make a copy of our binary QVW file and move it to the development path and eventually to the production server. So, maybe moving your QVW is easier than changing your path. This is certainly something you could do in your load process on your QMC.
This is assuming that your development server and production server are using the same folder structure.