This group hosts information related to the Qlik Deployment Framework (QDF). Providing best practices, libraries and utilities that facilitate the recommended setup and management of QlikView or Qlik Sense environments. An understanding of the Qlik platform is recommended before joining this group. Download QDF and documentation here: https://github.com/QlikDeploymentFramework/Qlik-Deployment-Framework/releases
I'm currently doing an internship where they've asked me to investigate the Qlik Deployment Framework in order to find out if and how we should implement it to replace our current Qlikview structure.
While investigating, I ran into a few things I'm unsure about, and in order to avoid having to spam these forums, I thought I'd gather a few before starting a thread.
If anyone could help me out, even by answering 1 or a few of these questions, I would greatly appreciate it
Thanks in advance!
1. I have not tested for some time however if you create sub-folders under the QVD folder variables are created. I.e. say you have QVD\Load QVD\xForm, QVD\xTract then you get variables vG.Load, vG.xForm, vG.xTract. I am not sure if the same features exist in other folders.
2. You can re-order the sub-folders. This is done in under 0.Administration\0.Template. Previously there was an issue when changing numbers. However I believe this was resolve in v1.7
3. Numbering is just for a sort order. So I would recommend just being consistent.
4. Archived files are an interesting point. Do you archive any other files in addition to application files? I.e. configuration files, variable files etc. I tend to leave in place so you can easily restore a version.
5. With Sense I use the QDF differently to View. I just point at the shared location to load the sub-routines etc. The primary reason is that in Sense we have data connections so I find the need for containers for each project to be overhead. In answer to your question the QDF will attempt to load the sub-routines locally and then to the shared location.
6. As per 5, i tend to use the QDF slightly differently in Sense than View. In saying that it is compatible. Importantly it ensures that a consistent approach is applied. Also if you leverage the more advanced features such as Load QVDs you can easily leverage artefacts across both sites.
7. I don't use the variable editor at all. Rather I just edit the related csv(s) directly with a notepad editor. I.e. notepad++ or similar.
Thank you very much for your response
Clear answers, but they do bring up a few more questions. I hope you don't mind.
1. When I try this for any container (even QVD), no new variables are created. Do I have to add these to the container map somehow as well? Or do I have to change something in the initiation files for this to work?
4. We currently only archive applications, QVDs and import files (mostly Excel). Variable/Sub/Config files aren't really used yet, but probably will be once the QDF is in place. The main reason we want to create an archive separate from the rest of the files is because they currently really clutter up our storage. In order to avoid this clutter in the new structure, I want to make sure there is a space to store old files so they don't just get left where they are.
Not really any new questions for 4, I guess it's just a matter of preference, as the archived files are rarely referred to in applications.
5. It does not seem like my QDF is loading subs from the shared folder when they aren't in the local folder. I've tried:
- 1.Init in local, rest of 1.BaseVariable and 4.Sub in Shared, initiate from local
- 1.BaseVariable in local container, 4.Sub in Shared, initiate from local
- 1.BaseVariable and 4.Sub both in Shared, initiate from shared
- 1.BaseVariable and 4.Sub both in local, initiate from local (this works, but isn't really what I want as I'd need to store a copy of these files in every container
I'm probably just doing something wrong, but I don't know what. Any ideas?
Again thanks a lot for your reply
Late to the party but I'll try to answer.
1. Whenever you create subfolders in any of the main folders you can just append them to the folder variable the new folder is in. So for instance I create 1.Extract, 2.Transform and 3.Load in 3.Include/3.Custom for all my models. I reference qvs files in those folders like so