QlikView: best practice of ongoing development on documentArticle Number: 000022029 | Last Modified: 2018/06/12
- QlikView deployment is done and running.
- Users are regularly using published QVW documents.
- Developers are doing ongoing development on the already published QVW documents in order to improve user experience or add new features.
- Avoid modification on existing QVW files.
- Reason: changes in existing QVW files are possible to break compatibility between QVW files and other related files such as .SHARED or .META files.
- Best practice: instead of modifying existing QVW files, please consider using different versions of the same file. For instance, instead of constantly modifying DOC.QVW, please consider publishing DOC_V1.QVW, DOC_V2.QVW, etc..
- Drawback of this practice: user generated contents(such as server bookmarks, charts, etc.) are not transferable between versions of documents.
- Avoid modifying existing objects, if modifying existing QVW files is inevitable.
- Reason: same as above. It is possible to break compatibility between objects in QVW files and records in other related files such as .SHARED or .META files.
- Best practice: instead of modifying existing QVW files, please consider cloning the objects then modify the cloned ones. Cloned objects will have new object IDs, which will force new records to be created in associated files. Original objects can be hidden or deleted.
- Drawback of this practice: information associated to the old object IDs(such as notes on charts) cannot be carried across.
- Avoid modification in the existing data model in any case.
- Reason: any change in data model may make the existing objects(bookmarks, charts, etc.) invalid.
- Best practice: if modification in data model is inevitable, always add items(fields, tables, etc), and never remove or rename anything. Doing so can ensure current reference to still be valid.
- Drawback of this practice: it will lead to an ever growing data model which can potentially cause other negative impact such as performance issue. Hence this should be avoided unless absolutely necessary.
Have a Question?
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.Submit a case
Experiencing a serious issue, please contact us by phone. View phone numbers and hours by region.