Keep the App–Content Library Link Intact When Promoting Qlik Apps Across Dev, Test and Prod
You update an icon or a header image in the content library, and in dev everything looks right. Then you export the app to test, import it, and the pictures are stale — or gone. The app that moved no longer points at the library it was built against, so every future image and icon update stops propagating. Many Qlik developers hit this exact wall when promoting apps across dev, test and prod: the content library link does not survive export/import, and nobody notices until a logo is wrong in production.
The manual export/import way
The usual route is to export the app as a QVF from dev, then import it into test and again into prod. The QVF carries the sheets, the script and the app's own objects, but its reference to a shared content library is resolved by name and ID on the source tenant. On the target environment that library either does not exist yet or has a different ID, so the link dangles.
Gitoqlok brings Git version control, collaboration and change history to Qlik Sense and Power BI — right inside your browser. Try Gitoqlok Free
To patch it, someone re-uploads images into each environment's library by hand, or edits object properties to repoint them. It works once. The cost shows up on the next change: an icon swapped in dev has to be redone in test and prod manually, every single time, with no record of which version is where. One missed step and a published dashboard ships with the wrong branding — and there is no clean way to roll back to the last good state.
How Gitoqlok keeps the app and its content together
Gitoqlok versions the app's attached content alongside everything else. When you commit from the Local Changes tab with App Objects selected, the images, icons and thumbnails uploaded to the app are written into the appcontent/ folder of the repository, next to objects/sheets/<id>.json and data_load_script/<section>.qvs. The attachments are no longer a loose dependency on a tenant library — they are part of the committed version.
To promote, open the target hub (test, then prod), click the Gitoqlok icon and choose Deploy from Git. Pick the repository, the branch and the exact commit, give the app a name and click Deploy. Gitoqlok rebuilds the app from that commit with its attached content embedded, so the same images arrive in every environment without re-uploading. Because each deploy is tied to a commit, the next icon change is one more commit in dev that you deploy forward — and any environment can be rolled back to a previous commit with Update. Data connections travel the same way: restore them on the target with Import Data Connections from the same repository.
