Display the user ID iin report headings

Mike:
The function is called @CurrentUser and you can create a parameter in crystal and make it hidden and not prompted and put @CurrentUser in the value then drop the paramter in the header.

Char

Thanks Char.

I created a test report in CR 2008, ver 12.3.0.601 with a single parameter and placed it on the report. I don't see an option in CR Edit Parameters or the LBI Maintain Parameters page to hide it, other than an option in the CR Edit Parameters form to prevent it from displaying on the Viewer panel

In CR, I tried a defailt value of @CurrentUser, but that just prints "@CurrentUser" on the report.

Can you tell me a bit mpre about how to set this up?

Thanks,

Mike
.

In LBI, you edit the parameter on the maintain parameters screen -( I'm not VPN'd to a client with LBI at the moment so forgive me if my wording is a litttle off). There are two settings you need to change, one is hidden and one is prompt - set these to hidden = true and always prompt = false. In the Default Value on this screen, you put @CurrentUser. I use it to control row level security within all of their reports..

Thanks Char, got it working.

It turns out that this technique only appears to work if you do not check the "Use Crystal Parameter Page" box on the report's Maintain Parameters form in LBI. We do check that box for a couple reasons, but primarily because if we don't, default parm values from the report don't appear, only defaults configured in LBI.

The main problem is those LBI defaults disappear when a report is republished, and need to be set again in LBI after each republish operation. Some of our reports have many parms with defaults for various account number segments and range limits, and it would be a huge PITA to try to have to recreate the defaults exactly after every republish.

Has this been an issue for you, and have you found any way around it?

Thanks,

Mike
.

What I do is to delete the parameters from the LBI maintain parameters screen except for the one parameter that is hidden that passes the UID to the report so the user then get's the Crystal prompted parameters for the others.

I would not have thought of that in 1K years!

Thank you very much for your help.

Mike
.

Char,

I read your post on @currentuser in the select statement. I have the field populating in the page header but I would appreciate an example of select statement with @CurrentUser. What bursting option would you choose from the LBI list?

This will save many hours if I can get it to work.

Thank you.

I chose not to use LBI "bursting" - this client is quite large and the amount of effort required to maintain the security schema within LBI would have required a lot more work than what I implemented. In their case, they secure reports by cost center and I created a script that runs each night an populates a table that draws the correlation to a User ID and the cost center(s) they see. I join this table to the other reporting tables and in LBI, I create a parameter called user ID, set it to not prompt and be hidden with the default @CurrentUser. On the maintain parameters screen, I append {Table.Field} = ?UserID.

You are so generous to help me with this.

Thank you very much.