Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
Venkatesh_Yellu11
Contributor III
Contributor III

Reload task

Qlik Sense enterprise working with the QMC environment.

I've created 4 Apps published in 4 Streams in different way:

Stream_1 : All Apps (APP_A, APP_B, APP_C, APP_D);

Stream_2 : APP_B, APP_C, APP_D;

Stream_3: APP_A;

Stream_4 : APP_A.

Since the APP_A is the same but published in 3 different streams, I would like to schedule ONE reload task for the APP_A that works for all the streams where APP_A is published, in order to optimize time. Of course, I would like do the same process for the other APPs.

Is this possible? And if this is possible, how can i do it?

Labels (1)
1 Solution

Accepted Solutions
Or
MVP
MVP

You can't actually publish the same app to different streams. If you try and do that, each will receive its own unique ID, so you now have multiple apps (that were created based on the same app, but they're still individual apps). 

This isn't something you'd generally want to do, but if you do insist on doing it, what you would probably want to do in this scenario is have one master app that loads the data, with all of the copies loading directly from the master's QVDs/Parquets/whatnot. You may alternatively be able to leverage Binary Load, depending on the specific requirements and situation. 

Do note that having four copies of the same app uses up more memory, which is likely to be undesirable. I would suggest looking into options that don't involve duplication. 

View solution in original post

1 Reply
Or
MVP
MVP

You can't actually publish the same app to different streams. If you try and do that, each will receive its own unique ID, so you now have multiple apps (that were created based on the same app, but they're still individual apps). 

This isn't something you'd generally want to do, but if you do insist on doing it, what you would probably want to do in this scenario is have one master app that loads the data, with all of the copies loading directly from the master's QVDs/Parquets/whatnot. You may alternatively be able to leverage Binary Load, depending on the specific requirements and situation. 

Do note that having four copies of the same app uses up more memory, which is likely to be undesirable. I would suggest looking into options that don't involve duplication.