topic Re: App on two streams and restriction on one app in Visualization and Usability

App on two streams and restriction on one app

Aurelien_Martinez — Wed, 18 Nov 2015 10:37:08 GMT

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

Re: App on two streams and restriction on one app

Levi_Turner — Wed, 18 Nov 2015 18:54:34 GMT

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

Re: App on two streams and restriction on one app

Aurelien_Martinez — Wed, 18 Nov 2015 18:55:41 GMT

resource.stream.name="Everyone"

Re: App on two streams and restriction on one app

Levi_Turner — Wed, 18 Nov 2015 18:59:40 GMT

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.

Re: App on two streams and restriction on one app

kp_qliktech — Wed, 18 Nov 2015 19:40:26 GMT

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

Re: App on two streams and restriction on one app

JonnyPoole — Wed, 18 Nov 2015 19:57:27 GMT

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.