Dataitems from Different Namespaces in FM

[sumesh2429]

Hi All ,

I am just creating a FM manager model . I have 2 fact tables called Claims & Subclaims. I have added this 2 fact tables in 2 different namespaces in Framework Called Claims Layer & Subclaims Layer .  There is a join between 2 fact tables at the database layer .

There are some dimension tables which are just associated  with the first fact table i.e Claims fact . We needed the same dimensions to be there for the Second Fact table in Framework manager . So i created a Query Subject with the same name for that dimension table in the Second Fact Table Namespace in Framework Manager .

For example : D_AGENT table is joined to F_Claims . D_AGENT does not have direct relation to F_SUBCLAIMS .  F_CLAIMS & F_SUBCLAIMS have a join between now .
Now i am able to pull a column from AGENT & Subclaims in the report and the query generated shows the joins properly
ie D_AGENT joined to F_CLAIMS & F_CLAIMS joined to F_SUBCLAIMS.

My issue is the users are able to pull columns from both the namespaces now into a single List  and the report does not throw an error . Ideally if we pull data from different namespace it should throw an error . I dont want to allow users pulling data from different namespaces into a single list .
How can i prevent that ? Is there any settings i can change in FM or do i change my joins or something else ?

Thanks,

[CoolP]

It doesn't, as long as cognos finds a way(related objects) to generate SQL for the request. Why don't you hide the other namespace from the Package or create two different packages if they are intended for different audience.


Thanks
Prasan

[sumesh2429]

Hi Prasan ,

I did think of hiding the namespace but then the users want to see all the namespaces which are available . Hence i cannot hide it .

Thanks,

[bi4u2]

If you want the report to generate an error when a user uses items from 2 namespace, you would need to ensure that the underlying tables are not related in the model and make sure the governor setting for 'cross joins' is set to disallow.

[sumesh2429]

If you want the report to generate an error when a user uses items from 2 namespace, you would need to ensure that the underlying tables are not related in the model and make sure the governor setting for 'cross joins' is set to disallow.

My governor settings is as per what you said but since in the database the joins are done properly i.e the dimension to fact join and fact to fact join , hence even though both facts are in different namespaces its allowing me to pull dataitems from both .

[Rahul Ganguli]

Hi,

Remove the join between the fact tables in database view.
Make sure there is no dimension related to both the fact tables (i.e. there should not be any conformed dimension).

For dimensions like time, create two aliases one joined with only one fact table in a namespace.

Regards,
Rahul