This may not be possible, but I wanted to see what some of the experts' opinions are here.
One of our users has created a report in Report Builder. I want to take this report, post it to a folder and allow her employees to run the report.
I've put it in a folder called "Reference Line Reports" and gave browser permission to a list of users. These users are able to run the report (without having access to Report Builder or the report model).
When they try to utilize the "infinite clickthrough" functionality, I get the following error.
If I give one of these users access to the "report builder" they no longer get the error. The problem is that we don't want them to run the report builder (giving unrestricted access). I just want to be able to give them a report builder report with the clickthrough ability.
I would like to disclaim that we have not upgraded to SP1 (or CTP SP2 yet). Has anyone seen a similar problem or know if this was something fixed in sp1?
Thank you,
Dan
Hi Teo,
By the way... kudos on the "Applied Microsoft Analysis Services 2005" book.
I don't know if I was clear enough with my problem. I've removed myself from the "System User" system-level role (so I no longer have ability to see Report Builder button). I've given myself every single role/task on the "Reference Line Reports" folder. I've also given myself every single task on the Report Model.
I am still able to run the Report Builder report (posted in "Reference Line Reports"). However, when I try to utilize the "infinite drill-through" I get the error.
Once I give myself the System User system-level role (with Execute Report Definitions task) and all tasks on the report model, I am able to view the report & it's infite drillthrough. This wouldn't necessarilly work for us, however, because this also gives me the Report Builder button.
I would be ok with everyone having the report builder button, but I do not want to give everyone access to see the report model. If i have the "view models" task on the report model, users can drill through (but this allows them to create reports through report builder). If I remove the "view models" task, the permissions error appears.
Maybe my problem is trying to post a Report Builder report to the Report Manager for all users to view and drill through?
Regards,
Dan
Yep, I could probably do that. At this point, however, it is probably just easier to write the report in BIDS and post it for them.
I guess I'm just not sure why they could execute the Report Builder report, but didn't have permission to drill through.
Thanks for looking into, Teo.
Regards,
Dan
|||The Clickthrough feature is essentially ad-hoc reporting, because the user can start with any report and continue drilling "infinitely"; hence the requirement for permission to the Execute Report Definitions task.
This is an interesting scenario, however. We will consider addressing this issue in a future release. At the very least the report author should be able to remove the Clickthrough links so users don't inadvertently click them and get an intimidating error message.
Thanks for the feedback.
|||Bob,
I appreciate the response. I'm glad to see it's more of an unforseen scenario in as opposed to something we have done incorrectly. I think it would be helpful to be able to allow users to clickthrough a report builder report without giving them access to execute report definitions.
In this scenario, we have a user who can author reports via report builder. Once she authors them, she will either keep them in her My Reports folder or we will post them for her immediate employees. We don't want to give the immediate employees "unlimited" access to the data - just restricted to the high-level summary view the report builder report gives.
We can also avoid having to re-create reports (summary and detail level views) in BIDS that have to be manually coded to drill through.
I do understand why this scenario might not be natively supported. Thank you for at least considering this scenario (or like you stated, at least considering the suppression of the intimidating error message).
Regards,
Dan
No comments:
Post a Comment