ODAG Links Break Every Time You Deploy a Base App? Keep the App ID Stable
Your On-Demand App Generation (ODAG) setup works fine in development: the selection app fires a navigation link, the template generates, users get their sliced data. Then you push the base app to test or production, and every ODAG link goes dead. Many Qlik developers hit this on every single release — the deploy itself is what breaks the dynamic-view links, and you spend the hour after each rollout re-linking by hand.
The manual way: replace the base app, then repoint every link
You build and validate in dev, then move the app forward. In the target environment you usually replace the published base app, or import a fresh copy and publish that. Either way you get a working app on the stream — and a brand-new app GUID.
Gitoqlok brings Git version control, collaboration and change history to Qlik Sense and Power BI — right inside your browser. Try Gitoqlok Free
That new GUID is the whole problem. An ODAG navigation link stores the ID of the base (template) app it generates from. Replace the app and the ID it pointed to no longer exists, so every ODAG link and dynamic view attached to it dangles. You reopen each navigation link, paste the new app ID, and re-test — for every link, on every environment, on every release. Miss one and users silently get stale or empty on-demand apps.
The Gitoqlok way: update the same app in place
Gitoqlok stops the ID churn by never replacing the app. Open the base app in the browser, click the Gitoqlok icon, and on the Local Changes tab click Save changes to commit the app to a Git repository — sheets, master items and the load script land as JSON files, and the app's GUID is written into the repository description. To ship a new version, pick the commit in the commit selector and click Update: Gitoqlok applies that committed state to the existing app instead of creating a copy. The GUID is untouched, so every ODAG link that targets it keeps resolving. See how Update works in the docs on Update and Roll Back.
For standing up a fresh environment the first time, open the target hub, click the Gitoqlok icon and choose Deploy from Git — pick the repository, the branch and the exact commit, and Gitoqlok builds the base app there. You wire your ODAG navigation links against that app once; from then on every release flows in through Update against the same app, not a replace, so the links you set up survive each deploy. The trade-off is honest: Deploy from Git creates one new app when the environment is empty, so the initial link setup per environment is still yours — but the repeated per-release re-linking that ate your rollout window goes away. Details in Deploy from Git.