Rest of the classes, Pmt and Tkt classes having measure objects.

My qurey’s are:
1) Select *
from event, tkt
where
event.ctseventid = tkt.ctseventid and venueid = 81

2) Select *
from event, pmt
where
event.ctseventid = pmt.ctseventid and venueid = 82

Note: I’ve joined this ‘tkt’ table to some other tables also. If I am going to give the condition ‘venueid = 81’ in the ‘tkt’ table, that will restrict the result for some other reports. That I don’t want.

Same for ‘Pmt’ table also.

If the only choice is ‘event’ table, can you pls tell me how it is possible??

Here is my illustration of a typical row level user restriction case .

Suppose we have 3 fact tables fct-1,fct-2,fct-3 and an user security table “sec_tbl” with two columns, country_cd and user_id

option-1: class restriction method

1. sec_tbl need to be joined to all three fact tables in designer
2. create filter with class restriction like sec_tbl.user_id = @Variable(’BOUSER’) applied to only fct-1,fct-2,fct-3 class.

now pull any object from fct class. the query will be like:

select fct-1.xx
from fct-1
,sec_tbl
where fct-1.country_cd = sec_tbl.country_cd
and sec_tbl.user_id = @Variable(’BOUSER’)

(The security table wont be that huge hence the extra join doesnt affect the performance of query.)

option-2: using BO designer’s manage security option:

1.Creat three restriction sets to the three fct tables like
fct-1.country_cd in (select distinct country_cd from sec_tbl where sec_tbl.user_id = @Variable(’BOUSER’))
fct-2.country_cd in (select distinct country_cd from sec_tbl where sec_tbl.user_id = @Variable(’BOUSER’))
fct-3.country_cd in (select distinct country_cd from sec_tbl where sec_tbl.user_id = @Variable(’BOUSER’))

2. Assign the above restriction set to group(s) in designer.

Now here is the query:

select fct-1.xx
from fct-1
where fct-1.country_cd in (select distinct country_cd from sec_tbl where sec_tbl.user_id = @Variable(’BOUSER’))

(Here the subqury is also not that costly)

One advantage of option-1 is, filter is applied even the filter table is not referenced, but to make the force join work the security table needs to be joined to required tables in universe.

Take an example of addition of new fact table..both the options need changes.option-1 add a new join and that of option-2 add a new restriction set.

2nd example: add a new object to the existing class, option-1 works great so as option-2.

Am i missing any advantage of the new feature over the existing one..