cancel
Showing results for 
Search instead for 
Did you mean: 

How to suppress master data attributes in Universe from BEx

Former Member
0 Kudos

Hello Gurus,

I have a 0customer in my Cube and I only have 4 objects checked as navigational attributes in the Cube ( Name, Address, State, Zip). I built a BEx query on this cube and I have dragged 0Customer and the 4 attributes under 'Rows' in the BEx query. Now when I build a universe on top of it, I am seeing all the attributes ( even the unchecked navigational attributes around 40 attributes of 0customer in the universe. Appreciate if somebody could please let me know how to avoid the unchecked master attributes displaying in the Universe (or) display only the attributes which are under display of 'Rows' in BEx instead of showing the entire attributes in the universe. Please provide suggestions other than hiding the unnecessary attributes in the universe level.

Thanks,

Kavit .

Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos

Hi,

It is not possible to change/ control anything in Universe Designer for a BEx query. If any change is required, it should be maintained at the BEx level. Universe Designer in case of a BEx just acts as a layer over BEx query.

Regards,

Rupali

Former Member
0 Kudos

Hello,

I have a similar problem but with thousands of objects...

Is there any solution available? I doesn't matter if I have to make changes in the BEx query or in the universe.

Thanks and kind regards,

Jule

sureshmandalapu6
Active Contributor
0 Kudos

Hi,

You can delete the unwanted objects from universe and keep what you need.

Regards,

Suresh

Former Member
0 Kudos

Hello,

thanks for your reply. How can I delete or hide all attributes without selecting each single object? I have a universe with more than 6000 attributes. Is there a process which can do this automatically?

Thanks and kind regards,

Jule

Edited by: Juliane Exner on Nov 30, 2011 10:37 AM

Henry_Banks
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

there's no quick way of doing this, apart from reducing the number of objects in your BEx query.

6000 objects sounds like trouble! performance may be poor, because too many requirements are being answered.

Regards,

H