Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Hide a column in BW Query

guillermo_m
Active Participant
0 Likes
537

Hi Gurus!

I'd like to hide a column for specifics users in a BW Query.

I flagged the InfoObject as Auth. Rel. and created an analysis authorization. I ran the query but I got "No authorization", when I checked the log I saw that the query is asking for full authorization value to that InfoObject. I tried with : (semi colon) value but I got the same result.

Is there any way to hide a column in a query (with authorization concept) avoiding to redisign a new query?

Thanks in advance.

Best regards,

Pepe

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
502

Hi Pepe,

You can achieve this with user exists. However, the easiest way is to create two different queries and hide the additional column in the query in which you doesn't require the column to be displayed.

Making authorization relevant requires authorization for all the users who execute the query.

Regards,

Raghu

Hi Gurus!

I'd like to hide a column for specifics users in a BW Query.

I flagged the InfoObject as Auth. Rel. and created an analysis authorization. I ran the query but I got "No authorization", when I checked the log I saw that the query is asking for full authorization value to that InfoObject. I tried with : (semi colon) value but I got the same result.

Is there any way to hide a column in a query (with authorization concept) avoiding to redisign a new query?

Thanks in advance.

Best regards,

Pepe

2 REPLIES 2
Read only

arpan_paik
Active Contributor
0 Likes
502

when I checked the log I saw that the query is asking for full authorization value to that InfoObject

Is there any way to hide a column in a query (with authorization concept) avoiding to redisign a new query?

For your existing query, above two are conflicting. So guess you have to move with redesign/new query.

Regards,

Arpan Paik

Read only

Former Member
0 Likes
503

Hi Pepe,

You can achieve this with user exists. However, the easiest way is to create two different queries and hide the additional column in the query in which you doesn't require the column to be displayed.

Making authorization relevant requires authorization for all the users who execute the query.

Regards,

Raghu