Its not something I've done but you could try relative paths - unlikely to work but worth a shot.
Alternatively you may be able to work something out using this
or system variables, but if your production and dev environments are all on the same machine I'm not so sure
Saw your explanation provided in the Post. It is Clear and I understood that we could define an Environment Variable inside the .nsq and then Change the Value of the Variable based on Test Server Deployment or Prod Server Deployment.
But, isn't it Similar to my Present Manual approach of changing the Path? I still need to Manually Change the Environment Variable by opening the individual .nsq which is still an Overhead.
As I asked in the Question
"if there is a way by which I could use ComputerName() and then Variables to store the above paths then kindly suggest."
Also, Thanks Thomas for the response.
No, Daniel's solution that uses Environment Variables in not similar to a manual approach.
If you have many connections in a manual approache you need to change all them manually one by one. With Daniel's you use the variable in all connections so you need to change only the variable value one time.
Environment variables are also very useful for templates. In Qlik NPrinting 16.* templates are files saved on a filesystem, so there is a path that can be created with EV and it could be different from development to production server. Thanks to EVs you will need to change only few variables (maybe only one) when moving templates from a server to another.
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.
We have only 1 .qvw in the Connection for 1 particular .nsq. Hence, I wrote that The Suggested approach was still an overhead.
Yes, indeed if we have multiple .qvw in the Connections then Daniel Suggested Approach(using Environment Variable) will lessen the Manual Overhead if not eliminate.