Hi Jason,

There is a table called CurrentLogin, which will tell you who is logged into the computer, not TMS, which is better than nothing.

I use this field to control visual access to fields on reports.  The table sits independent, i.e. doesn't link to any other table in reports, which Crystal doesn't like but will tolerate.

Thanks,
Carole

From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Krantz, Jason@Parks
Sent: Tuesday, April 05, 2016 3:16 PM
To: [log in to unmask]
Subject: Crystal Reports and Department Level Security for Current Location Transaction

Hello all,

We have been revising some of our older reports and came across an interesting puzzle that maybe some of you have already solved:


*         Our view/read-only security profile for departmentally-controlled modules does not allow users to view Current Location Transaction for Object Components.

*         Our data entry/read-write security profile for departmentally-controlled modules does allow users to view Current Location Transaction for Object Components.

*         Any given user may have data entry rights (or higher) for a handful of departments, while the remaining departments are given view-only or no rights.

Using the HierarchyID for the correct Current Location Transaction entry in SecGrpHierXref, along with the UserID parameter passed into SSRS by TMS, we can easily hide or show this information in our SSRS reports conditionally for each object, but we are currently at a loss as to how we might accomplish this within our older Crystal reports. Is there an easy way to pull the current TMS user's UserID, LoginID, or SQL Server/Active Directory user name into Crystal Reports? We're currently using Crystal Reports 2013 SP5, if that helps anyone.

Given the number of departments (>70), and the fact that we're not dealing with Overall security, restricting access to reports or hardcoding department-specific reports are not viable solutions.

Thanks,

Jason Krantz
IT Student Assistant
California State Parks
Cultural Resources Division

To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email:

signoff TMSUSERS

// eoj

You will receive a confirmation that your subscription has been removed.

To unsubscribe, send an email to [log in to unmask] with the following commands in the body of the email:

     signoff TMSUSERS

     //  eoj


You will receive a confirmation that your subscription has been removed.