Skip to main content
Announcements
NEW: Seamless Public Data Sharing with Qlik's New Anonymous Access Capability: TELL ME MORE!
cancel
Showing results for 
Search instead for 
Did you mean: 
Aurelien_Martinez
Partner - Specialist II
Partner - Specialist II

App on two streams and restriction on one app

Hi community,

I have two questions for you :

First : Can I have one app publish in two streams without duplicate them ? or a mean to emulate that ?

Second : I want to restrict access in one app and I have try to create security rules like https://community.qlik.com/thread/173848, but I think the standard rules blokc my rule.

My rule : ((resource.name="AdWords") and (user.name!="Toto"))

Thank you

Help users find answers! Don't forget to mark a solution that worked for you!
1 Solution

Accepted Solutions
Levi_Turner
Employee
Employee

  1. No, it's currently not possible. Applications can only be published to a single stream.
  2. What stream is this application published to?

View solution in original post

5 Replies
Levi_Turner
Employee
Employee

  1. No, it's currently not possible. Applications can only be published to a single stream.
  2. What stream is this application published to?
Aurelien_Martinez
Partner - Specialist II
Partner - Specialist II
Author

resource.stream.name="Everyone"

Help users find answers! Don't forget to mark a solution that worked for you!
Levi_Turner
Employee
Employee

Check out stream name StreamEveryone, description The default stream called Everyone should be visible for all users and all users should be able to publish to it.

kp_qliktech
Contributor
Contributor

1) First : Can I have one app publish in two streams without duplicate them ? or a mean to emulate that ?

-- to the above qns did you try this - import app publish to the stream1 , import the same app again and now publish to stream2

JonnyPoole
Former Employee
Former Employee

You can design a single app and then do a binary load of that app into 2 different apps (or you can use the same QVDs as the source instead of binary load). T

he 2 different apps could be published to 2 different streams.  I know this duplicates the app BUT the benefit here is that you are not duplicating effort.. both apps would be auto-reloaded from the disk based app or QVDs so everything is propogated and kept in sync. I would not do this with apps that have 100M rows, but 1M row apps are a dime a dozen and very scalable.