When 'Always One Selected Value' Resets on Every Qlik Release — and How to Stop It
You set a field to 'Always one selected value' in Qlik Sense, test it, and ship the app to the next environment. Then someone opens the released copy and the selector behaves like any ordinary field again — the property is back to its default. Many Qlik developers hit this during app migration without data: the field-level setting silently reverts, and nobody notices until a user complains that a mandatory single-select filter now lets them pick five values at once.
The manual way: re-apply the setting on every release
Without version control, the field property lives only inside the live app, and a migration that moves the app definition between environments doesn't carry it reliably. So the fix becomes a checklist step: after each release, open the Data model viewer or the field settings, find every field that needs 'Always one selected value', and tick it again. On an app with a dozen guarded fields, across DEV, TEST and PROD, that is the same tedious re-adjustment every single time.
What breaks is trust in the release. The setting is invisible in a normal walkthrough, so a missed field slips straight into production. To cope, teams fall back to keeping full-data .qvf backups of the previous working version — heavy, slow to move, and full of production data you'd rather not copy around — just so they can restore the exact field behaviour if a release goes wrong.
Gitoqlok brings Git version control, collaboration and change history to Qlik Sense and Power BI — right inside your browser. Try Gitoqlok Free
The Gitoqlok way: the field property is part of the versioned definition
Gitoqlok commits the complete app definition, field settings included. When you click the green Gitoqlok icon on an app and open the Local Changes tab, selecting App Objects in the Save changes dialog writes the app's fields and properties to the repository as fields.json, properties.json and appprops.json. The 'Always one selected value' flag is stored in those files like any other property — so it is now captured, diffed and restorable, not floating loose inside one app copy.
To promote the app to another environment, open the target hub, click the Gitoqlok icon and choose Deploy from Git: pick the repository, the branch and the exact commit, name the app and deploy. The new app is rebuilt from the same committed definition, so the field keeps its single-select setting with no manual re-ticking. If a release ever does drift, select the last good commit in the commit selector and click Update to roll the app — and its field properties — back to that state. See Update and Roll Back.
TIP
Gitoqlok commits the design, not the data: script, objects, fields and properties — not the loaded rows. You get a reliable restore point for field behaviour without hauling multi-gigabyte full-data .qvf backups between environments.
The repeating post-release fix disappears, and so does the reason for risky full-data backups: the one thing you were protecting — the exact app definition, down to the 'Always one selected value' field property — now lives in Git, versioned and reproducible on every release.
