Crystal Security

This is exactly hte functionality with in Reporting Services called Rights Management. It will allow you to set up rules and then burst your reports to the users based on these rules.

If you build your reports using Lawson's OLE-DB Connector then the data level security assigned to each user will be applied. If you're publishing within LBI then set the data settings to use the ID of the person logged in.

You can also set Bursting Rules within LBI on any Crystal Report.

We use ODBC connections to get to the Lawson tables - David is that similar to the OLE-DB connector?

Matt - if we have the licensing for Crystal does that give us the licensing for Reporting Services? Or is this a separate product?

Reporting Services is licensed with Lawson Business Intelligence (not to be confused with Microsoft SQL Server Reporting Services). What "Crystal" products do you have licensed, Business Objects Enterprise, Crystal Enterprise, etc? If you have any of those there are some other options.

If your reports connect vis ODBC you wont be able to utilize Lawson OLE DB Connector. One thing to keep in mind about the Lawson OLE DB connector is that performance is poor and relationships are very shallow. Search this forum and youll find some pretty in-depth threads about this topic.

Reporting Services is part of LBI, do you own Lawson Business Intelligence?

You can handle like Matthew said in rights management or filter the reports based on user id so they see only the AU's they need. We use a parameter on reports to look at your user id in reporting services and pulls the data you are assigned to see (attributes for managers).

We do have LBI. Thanks! I will share this with our tech people and hopefully this will give them a starting point.

Totally agree with Matt.Like Matt said if you use Lawson's OLEDB connector, the security is present but the performance is very slow and there was a time where we had to convert from OLEDB to ODBC for all of our reports.

But you can still use rights management with ODBC reports where you set a right with your element mapped to a field on the ODBC reports. We actually create a role for the user which is not the user-id but the position or the department role for the user and utilize this for rights management.

This way when the user changes departments or leaves the organization or changes jobs internally we do not have to change the user-id but manitain it at the security level where we just change the user-id from that role. This avoids us mainataining rights management and we maintain it at the security level.