Qlik Sense teams keep duplicating apps and losing the good version — here's the fix
Put two or three developers on one Qlik Sense space and the same thing happens every time. Nobody can reassign app ownership, so people duplicate the app, rename the copy, work on it, and delete the old one when they think they're done. A week later the space holds "Sales v2", "Sales_final", "Sales (Ann's copy)" and "Sales FINAL fixed" — and no one can say which one is the version that should go to production. Admins can't hand out QMC rights to sort it out without exposing everything else on the server.
The manual way: duplicate, rename, hope
Without version control, a shared app is passed around by copying. A developer duplicates the published app into their personal space, edits a few sheets, and publishes a replacement — or asks whoever owns the stream to do it. The next person duplicates that, and the chain grows. Changes live only inside whichever QVF happens to be open, and the only record of "who changed the KPI and when" is people's memory.
Gitoqlok brings Git version control, collaboration and change history to Qlik Sense and Power BI — right inside your browser. Try Gitoqlok Free
The cost shows up at the worst moment. Two developers edit the same sheet in separate copies and one quietly overwrites the other. A measure gets reverted because someone rebuilt from an older duplicate. And when a published app breaks, there's no clean previous state to roll back to — just a pile of ambiguous copies, each a little different, none of them labelled as the truth.
The Gitoqlok way: one repository, a branch per developer
Gitoqlok links a Qlik app to a single Git repository, and that repository — not any QVF on the hub — becomes the source of truth. Open the app, click the Gitoqlok icon, and the popup opens on the Local Changes tab; Create Repository makes the repo, Save changes writes the first commit. Instead of duplicating into a new app, each developer takes a copy and, in the Gitoqlok popup, connects it to the same repository as a branch (named after them by default, e.g. ann). Everyone now commits to one history: every commit is a dated, named restore point in the commit selector, and the link survives renames because Gitoqlok identifies the app by the ID stored in the repository description, not by its name.
When it's time to bring the work together, the app owner opens the master app's overview and clicks Compare Sheets in the Gitoqlok Helper bar, then picks a colleague's branch. The Sheets Comparator colours each sheet card — green for new, yellow for changed — so you see exactly what was touched. From a yellow sheet you jump into the Diff Viewer and merge chart by chart, or merge branches with a pull request on GitHub, GitLab or Bitbucket and hit Update to pull the result back into the master app. The space stays at one app; the "versions" live in the repository as commits and branches you can read, compare and roll back — described step by step in the Team Workflow guide.
All the ways to restore an earlier version — one sheet, one measure, the whole app or a deleted app: How to Roll Back a Qlik Sense App to a Previous Version.
