ODAG Links Disappear After API's Delivery and Duplication in Qlik Sense
Hello everyone,
I am encountering an issue with accessing ODAG links in Qlik Sense for a non-RootAdmin user. Here is the context:
Source Environment :
I created a Qlik Sense application with ODAG links pointing to template applications.
When this application is accessed by a non-Admin user, the ODAG links function correctly in this environment.
Delivery to Target Environment (Delivery Steps) :
I export the application from the source environment and import it into the target environment using the QRS API.
I recreate the ODAG links in the target environment using the ODAG API.
I update the application's ODAG links using the Engine API.
Issue :
When the Admin user opens the application, the ODAG links function correctly in the target environment.
When a non-Admin user opens the application via the hub, the ODAG links are greyed out and absent from the list.
When the non-Admin user connects to the Dev Hub / Engine API and accesses the delivered application, no odagapplink is visible in this application for that user.
If the Admin user connects to the Dev Hub / Engine API and opens the same application, the odagapplink appear.
Additional Observations :
In the source environment (where the ODAG links were manually created in the application), non-Admin users can see all odagapplink in the Dev Hub / Engine API.
When the Admin user duplicates the application, the non-Admin user can see the ODAG links in the duplicated application.
In the Target Environment (where the application was delivered via APIs) :
When the Admin user duplicates the application in the hub or QMC and then opens the new app, no ODAG links are available. Opening the duplicated application in the Dev Hub / Engine API shows that no odagapplink exist.
Questions :
Do the ODAG links created via API (QRS + ODAG + ENGINE) not have the same visibility as the links manually created in an application?
Is there a missing step during the delivery of the application via API?
Why do applications delivered via API lose their links when duplicated?
Just to clarify, were the links created with API directly for a published application? Any server-side object created directly in a published application tends to exhibit behavior similar to what you describe, in my experience, though I haven't encountered it with ODAG specifically because I never created ODAG connections in a published application.
Just to clarify, were the links created with API directly for a published application? Any server-side object created directly in a published application tends to exhibit behavior similar to what you describe, in my experience, though I haven't encountered it with ODAG specifically because I never created ODAG connections in a published application.
