Qlik Community

Qlik Sense Deployment & Management

Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.

fergicide
New Contributor

AppID and streams - republishing to alternate stream use case

Consider this use case.

  1. App XYZ published to Stream-1.
  2. Single Configurator utility used to get direct URL to this application on the Qlik Server, e.g.
    https://myqlikserver/sense/app/a2067168-2e62-416d-9279-5788f0ae2ce5
  3. URL to access the app is provided to developers for other internal systems, so that those systems can link across to App XYZ in Stream-1 on the Qlik server.
  4. Requirement to publish App XYZ to a different stream: Stream-2.  Perhaps App XYZ was published to Stream-1 in error.  Because there is no ability to "unpublish" a published app, nor any ability to move it to a different stream, the only option is to duplicate App XYZ and publish this copy to Stream-2, then delete the original copy from Stream-1.  This means the copy of App XYZ in Stream-2 has a newly generated AppId and the URL link provided to developers in Step 3 is no longer valid.  Developers will need to update their links to switch the new AppId for the old one.

QUESTION: Why is there no facility to either (1) move a published application between streams, thereby preserving its AppId; or (2) unpublish a published app then republish to a different stream, which would preserve its AppId, meaning no need to udpate any direct URL links.

Preserving an application's AppId on the server is crucial for maintaining working links from third-party systems, as described above.

Thanks!

1 Solution

Accepted Solutions
barryharmsen
Contributor II

Re: AppID and streams - republishing to alternate stream use case

Very late response

You can use pgAdmin to log into the Postgres database (use port 4432 instead of the default 5432) and manually update the Stream ID for an app. Be sure to stop the Qlik Sense Repository Service while you do this.

For example:

UPDATE public."Apps" SET "Stream_ID" = '8c661fd2-5105-499f-8458-689370731a37' WHERE "ID" = '847ef781-2ede-46ea-b129-764cbabc8f01';

(Stream_ID is the ID of the stream you want to move to, ID is the ID of the app that you want to move)

8 Replies
dezrrehm
New Contributor

Re: AppID and streams - republishing to alternate stream use case

I'm going to bump (necro?) this because I'm on the cusp of an implementation and have already run into this.

Either this and/or the ability to publish the same app into multiple streams, simplifying maintenance and access control.

Vegar
Valued Contributor

Re: AppID and streams - republishing to alternate stream use case

fergicide: Did you ever figure this out? In my case it not important to maintain app id, but I want to transfer all user sheets and user published sheets.

Please ekskuse my Norglish and Swenglish typos.
Not applicable

Re: AppID and streams - republishing to alternate stream use case

I am having the same issue as vegar.lie.arntsen‌. I can not publish an already published app to another stream, because that would mean all user sheets and user published sheets would be gone. Is there really no solution to this?

jfkinspari
Contributor III

Re: AppID and streams - republishing to alternate stream use case

Bump.

Anyone found a fair way to move a published app to another stream maintaining associated app objects?

Vegar
Valued Contributor

Re: AppID and streams - republishing to alternate stream use case

Unfortunately no.

What we are planning to do to solve our problem is to convert the Everyone-stream into a more limited business stream and thereafter create a new empty everyone stream as a replacement for the old one.


It is not an optimal solution, but it meet the business needs at the moment. I would really like to se a better solution where we actually can move the application with user generated content between streams.

Please ekskuse my Norglish and Swenglish typos.
barryharmsen
Contributor II

Re: AppID and streams - republishing to alternate stream use case

Very late response

You can use pgAdmin to log into the Postgres database (use port 4432 instead of the default 5432) and manually update the Stream ID for an app. Be sure to stop the Qlik Sense Repository Service while you do this.

For example:

UPDATE public."Apps" SET "Stream_ID" = '8c661fd2-5105-499f-8458-689370731a37' WHERE "ID" = '847ef781-2ede-46ea-b129-764cbabc8f01';

(Stream_ID is the ID of the stream you want to move to, ID is the ID of the app that you want to move)

fergicide
New Contributor

Re: AppID and streams - republishing to alternate stream use case

What we ended up doing is writing an app to compose the direct URL link to streams, apps, and sheets.  This app writes out the CSV data to text file, and an SSIS job reads in the CSV data to populate a table in our SQL BI database, which then feeds a View.  All systems can then query this View to get the direct URLs to any app, stream, or sheet.

So, if any app gets republished with a new ID, our systems pick up tthis change automatically by reading at startup the latest values (full URL links) from the View.

lucienorrin
Contributor

Re: AppID and streams - republishing to alternate stream use case

We use NPrinting and have had similar situations where customers wanted to move an app to another stream. Well...every NPrinting report had to be reworked with a new appID. Some app objects were orphaned or deleted and needed to be recreated, which had to be reimported into the NPrinting report.

Community Browser