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.

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.