How to get Current Log in BO user name in data access driver

Question

In universe, to get the current log in user is via @Variable('BOUSER').
Right now, I need to be able to get the user name in the data access driver. I am writing a customized data access driver because we need to patch some where clause on the the query generated by the universe based on the logged-in user info. I only think of using end_sql parameter or adding an universe level filter to patch the @Variable('BOUSER') to the query, which would not work if user want to use customized query.
Can anyone tell me how to get currentBO user name from connection server ? or how @Variable('BOUSER') is translated into the logged-in user name in the universe?

Answer 1

Shweta,
The link you provided was the Auditor guide for BO 6.x, I'm not sure it that is going to help Karen or not.
Karen,
There is function called connection
(usage:  =connection([Query Name]), where [Query Name]
denotes the name of the tab for the query under Edit Query)
Here is some of the output from connection:
4;ODBC18;MS SQL Server 2000166; VERSION=7; USER=xxxxx;
PASSWORD=; DBTYPE=Relational; DATABASE=xxx_xxxx;
ODBC_USER=xxxxxx; ODBC_PASSWORD=; BO_DSN=xxxx_xxxx;
BO_DRV_CONNECT_MODE=0; 224; VERSION=6; Name=xxxxx; Shared=4;
LoginTimeout=600; Timeout=600; Pool Time=60; Array Fetch Size=10;
Array Bind Size=5; RecommendedLenTransfert=1000; Password_Encryption=x;
AliasTable=; MeasureDimension=; Hint=; ConnectInit=; ArrayFetch=1;
I'm not sure if this info helps out either, being that connection provides info on a post-processing basis and it sounds like you need to get out ahead of the SQL generation.  The @variable('bouser') would seem like the place to be, however, in allowing custom SQL to take place you loose the bouser due to an individual could customize the SQL to the point that it gets unwantingly yanked out.  The end_sql might be your answer...
Thanks,
John