ODAG navigation links are broken when selection app is deployed to another Qlik Sense site

[Sonja_Bauernfeind]

When moving an ODAG selection app to another Qlik Sense site (for example from DEV to PROD environment), the ODAG navigation links in the selection app are broken and have to be recreated.

The user may see the button with "Invalid" stated or just red as seen in the below example:

 

Environment:

• Qlik Sense Enterprise on Windows, April 2020 and later

This is a known limitation of Qlik Sense since the September 2018 release. Currently, ODAG links point to AppID of template apps, which become invalid when being migrated to another Qlik Sense site because template AppIDs are not the same.

R&D is considering an improvement/feature request for a configurable AppID in ODAG links, which would allow the migration of ODAG selection apps from one Qlik Sense environment to another.
 

Active Feature Request:

Get a configurable AppID in ODAG links

Resolution:

! Qlik has previously received feedback on this feature and recorded the request for future review.  For up to date information and to express you would like the Feature implemented please review and vote on Get a configurable AppID in ODAG links.

.

Workaround(s):

Manually:

1. Import the target template app and publish to the desired stream in production

2. Import the summary app to a ‘my work’ stream in production – this requires the node purpose to be set to ‘Development' or ‘Development and Production’

3. Edit the app and correct or re-create the ODAG Navigation link(s).

4. Publish the updated App.

[Patric_Nordstrom]

Meanwhile  the recommended approach is to create ODAG links in using the API when moving to a new environment.

https://community.qlik.com/t5/Knowledge-Base/Qlik-Sense-Move-an-app-with-Dynamic-Views-to-a-QAP-envi...

[AndrewMcIlwrick]

This has been a helpful article. But unfortunately a major headache for our plans to automate QVF deployment - we will review the API approach as well.