BOUSER In Universe connection

[Former Member]

Hi All,

We have Implemented the BOUSER Variable in the END_SQL Parameter Of universe to fetch the BOXI Users who are running the Reports SQL in the database by looking at the query.

However at times the User use the Custom Sql functionality of the Webi and that By passes the Universe  Parameters and the User is not fetched in the SQL.

what I think is while using the custom sql  the universe Connection will still be used , My question is can we   Put some parameters in the connection like Something in connectinit or Hint .( we are using oracle) to fetch the details of the boxi user

Also , we have to keep the Rights For Custom SQL and edit query for users as this is business Requirement.

BO XI 3.1 SP 2

Thanks

[Former Member · Accepted solution]

Issue is resolved after passing session parameters in connectinit ,

thanks everyone

[Former Member]

Hi Kultar,

How are you doing?

Yes, even if the end users are using "Custom SQL" they have to use the same connection.

What I am not getting here is even if you have a parameter set in "END_SQL" it will not be removed if you select the option of "Custom SQL".

I am sure your users are removing this while pasting their own SQL statement.

Regarding connectinit and HINT they have their own concept but I am sure you can use this

@variable('BOUSER') thing in connectINIT also.

Thanks,

Vivek

[Former Member]

Hey Vivek,

I am doing good

Yes the Problem is that user are omiting the BOUSER Parameter when they use the CustomSql option.

I have tried using the @variable('BOUSER') in connectinit , the connection tests OK However while running a report error comes Out SQL statement cannot be prepared.

we are commenting it /* @variable('BOUSER')*/ and passing it through connectinit , does Not work For Me

[Former Member]

Used the

/* + @variable('BOUSER')*/ in the HINT again does Not work .Or i Might not be aware how to retrive In dbase side .

the connection is Ok , reports Run fine , Bit when I see the Sql in database , No value For BOUSER and nothing specific In the SQL.

Is there another way or something else needs to be checked at Dbase side

[former_member188911]

Hi Kuitar,

try the syntax suggested here

https://service.sap.com/sap/support/notes/1494759

the difference is that there are no spaces or other characters

If you still experience problems please open a support message with the Semantic Layer component  

thanks!

Best regards,

Simone

[Former Member]

Hi Simone,

we have used that already and works  however it works Only when Query used By BO is used.

If we use custom SQL and ommit the BOUSER will Not be there in the SQL retrived from dbase