Skip to content

Restoring a Qlik App Without Scrambling Community Sheet Ownership ​

You restore a Qlik Sense app from a backup — a QVF re-import, a duplicate pushed back over the published version — and the next time the team opens it, the community and personal sheets are gone. Sheets that belonged to individual analysts have collapsed into the base app under a single owner, and what used to be a handful of curated base sheets is now a pile of hundreds. Many Qlik developers run into this exactly when they need restore to be reliable: during a recovery.

The usual way: export, re-import, and hope ​

Without version control, a backup is a QVF file. You export it from the QMC or the hub, and when something breaks you re-import it as a new app or duplicate-and-replace the published one. The binary carries the data model, the script and the base sheets, but a re-import creates a fresh app object — a new app ID, a new owner.


Gitoqlok brings Git version control, collaboration and change history to Qlik Sense and Power BI — right inside your browser. Try Gitoqlok Free


That is where sheet ownership scrambles. Community (public) and personal (private) sheets are tied to the users who made them in the original app; a QVF restore does not reassign them, so they land in the baseline under whoever ran the restore. You cannot restore just the one broken sheet either — it is all-or-nothing, and you have no record of what the app looked like the moment before it broke to compare against.

How Gitoqlok restores in place, object by object ​

Gitoqlok versions the app's design directly from the browser instead of relying on QVF round-trips. Open the app, click the Gitoqlok icon and the Local Changes tab, hit Save changes and pick a commit message — each sheet is stored as its own objects/sheets/<id>.json file in the repository, alongside the load script sections and bookmarks. Every commit is a reviewable restore point, and it is linked to the same app by ID — Gitoqlok writes that ID into the repository description and never re-creates the app.

To recover, pick the commit in the selector and click Update. The arrow next to Update lets you restore only what you need — script, objects, bookmarks, attached files or automations — so you apply yesterday's layout to the live app without touching everything else. For a single sheet, open the Diff viewer or Time machine from the green Gitoqlok button, compare the committed version against the current one, and Apply Commit to roll back just that sheet. Because you restore into the existing app rather than importing a new one, the app object — and the ownership attached to it — stays intact. See the Update and Roll Back docs for the full flow.

Gitoqlok by Motio