We have several subject oriented universes accessing a vendor database. We need to exclude certain data to all users. The restriction can be applied in a specific security dimension table which can join to the various fact tables in the subject oriented universes. How do we ensure that the join to this security dimension table is automatically included in every generated query by any user. The fact tables can be quite wide, 50 - 100+ metrics and at the moment we have 8 subjected oriented universes with more planned. A suggestion was to include the table in the object property but that is potentially 800+ objects that would have to be touched.
You could try a Class Filter for something that forces the join to be included. Have it based on one of the join fields maybe. Class Filters will automatically be applied whenever an objects is selected from the class it is created in. It would be ideal if there was one class that contains objects that would always be included in every report put probably isn’t realistic. You may have to create multiple Class Filters to make sure the join is added in every time.
Thank you. Unfamiliar with adding a Class filter which would force a Join. I viewed Manage Access Restrictions, in which a Class can be hidden, a table could be remapped or add a where clause to a table but not forcing a join. Can you direct?
In the Condition View of the Universe Design Tool,
You can create a filter. Looks like you can create one that would be manditory for the universe as a whole, not just a specific class.
You could try creating something like this:
It won’t be visible to the users.
