Most of the time, we separate the 2 states of an application: development and use of it (called production). Because the development state is an instable state: developers work on it, add new functionnalities that do not work properly ... the users should not access it.
One of the difficulties is to move from one environment (development) to the other (production) because these 2 environments are different (it would be very expensive to have a development environment whch would be the same as the production one). Normally, you should never write a single line of code when moving from one environment to the other. So, how do you change the read of files in a developement environment (a specific directory or a specific database) to a production environment (another drectory, another database) without changing the code ? or at least with the minimum of change ?
The answer is by setting vPath variables that you will use always in the later code of your application. These vPath variables may be set through an Include statement, through basic commands (but you will need to modify some code) ...
Production Path means from where the end user is accessing your dashboard.
Development Path means the file path where you are doing the development.
For Example: if you have a clusted environment, then the file developed on one server will be productionized onto a shared path between all the servers which are in cluster. So this Shared path is Production Path and the server onto which you are developing the dashboard, that respective qvw path is your development path.
Development Path - The machine in which you develop qlikview dashboards and the files like qvd, Excel file paths in you local machine is called development path.
Production Path - The machine which you deploy your dashboards and the files like qvd, Excel file paths in you Production server machine is called Production path.
This may or may not be same sometimes. But it is a good practice to maintain the same paths, so that you don't need to change everytime when you deploy dashboards in production.
Most of the time, we separate the 2 states of an application: development and use of it (called production). Because the development state is an instable state: developers work on it, add new functionnalities that do not work properly ... the users should not access it.
One of the difficulties is to move from one environment (development) to the other (production) because these 2 environments are different (it would be very expensive to have a development environment whch would be the same as the production one). Normally, you should never write a single line of code when moving from one environment to the other. So, how do you change the read of files in a developement environment (a specific directory or a specific database) to a production environment (another drectory, another database) without changing the code ? or at least with the minimum of change ?
The answer is by setting vPath variables that you will use always in the later code of your application. These vPath variables may be set through an Include statement, through basic commands (but you will need to modify some code) ...
