Is view time security part of Crystal Enterprise 10 professional edition? Does this require an add-on product such as APOS? Is business views necssary to combine multiple data sources or can it be done directly from Crystal Reports 10? Please explain.
Thank you for the response. I am not sure about "run-time security". What I am looking for is "view time security". For example, a report groups on Doctor and there are 500 doctors. Each doctor that looks at the report sees on the records that belong to them. I assume this will be by NT or AD login information.
The functioality you want can be had by using Business Views in CE 10. Using the Business Views manager, you can set up your data connection(s), pick which fields you want to be exposed, and set up filters on the row level or column level. It is these filters that you would set permissions to using your CE group(s) and user(s).
Hi,
Ok, one more ( for now) question..
How are you calling the report ( EPortfolio, custom code..)?
If you create a parameter and have the user enter their UserId ( or any identifier that exists in the data ) you could use the parameter value as part of the selection criteria.
dbreed35, from what you are saying does that mean we do not need the APOS view time security add-on?
turkbear, we want to schedule the crystal 10 report in CE10 and then have the user come in through the browser and go to a directory that has the report already run. When they click on the report they should only see data where they have permission according to there login id. The report will contain data for all the users.
No, you would not need the APOS security add-on. You can run the report once, and then let the different users log in, and view that report. Depending on how you defined the filters in the business view, that user would only be able to see the data that they have permission to see, even if the report has already been run for all users.
Would it be possible for you to provide a simple example of the functionality?
I’ve got a profit and loss statement for about 100 locations and currently we get our users to provide a password to control security. It would be nice if I could eliminate this.
I found very little in the BV guide regarding row level security.
I would suggest walking through the tutorial in the BV Help file. That will at least get you started and show how to set up the basics.
After that, open up your Data Foundation. Create a filter and edit the rights. Apply the rights to a group or user. Whenever a user from that group logs in and view the report, that filter will be applied. It even works if that users is creating a report off that view. Since they have to log into CE to get access to the Business View (it is stored in the repository), the filter will apply.
Also, if someone with full access runs the report in CE and creates am instance, if one of those users logs in, and views that report, their filter gets applied.
I hope this explains it enough. Let me know if I need to add more detail.
I’ve played with the BVs briefly and couldn’t figure out how to associate a CE user with a location. The BV guide was absolutely no help at all. I’ll do as you suggest and work through the tutorial in the help file. (Didn’t even realize there was a tutorial.)
Hi,
To associate a user ( or group of users ) with a location, create groups in CE and make the relevant users members of the correct group..
For instance, we have 9 district offices, so I have 9 groups with the users that need access in each of the districts as members..When they log into CE to run the reports, they only see the data from their district, due to the BV filters that I created...I also have, in each group, a subgroup that is allowed to see some confidential fields in the report and use the field ( column) - level rights assignments to handle that.
BVs may be, for many admins, the most powerful feature of CE10..
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.