Publisher data reduction

[Anonymous]

Hi guys,

I would know something more about Publisher.

Let me present the following scenario:

I've some "normal user" and one "super user".

Each user has to manage the own data only; the super user has to see  all the informatin available.

What Publisher does exactly in this case ? Does it create an information set for each normal user ?

And what it does concerning the super user ? Does it create another set with the whole data set ?

Is there anyone who can give me some indication ?

Thanks in advance

stefan

[Alexander_Thor]

Hey Stefan,

Yes you totally correct. Publisher has a feature called loop and reduce which does exactly what you say, it will loop over for example a dimension and create smaller applications with only a sub-set of data related to that dimension value

Another way to limit data access in a application would be section access. Which could also be an approuch that would suit your need. Then you only have one application but apply row level security within that single application. There is great material on the community if you do a search for section access.

Then of course you use both loop & reduce and section access together to create for example region specific applications out of a master application and then apply row level security in that region specific application.