I have asked questions relating to this subject before and many replies from this list have helped greatly but I have now run into a problem. I am limiting rows for individual users from within the Supervisor module. When I originally tested this on a very simple report using only the objects that were included in the WHERE clause it worked perfectly. However, I have now tried to login as the user I have restricted and refresh a standard report of ours, but it is not limiting anything. There are many objects in the report that are in the tables I am restricting but the object that my where clause includes (where employee = “John Doe”) is not in the report. Why isn’t it working? When I look at the SQL for the report, the where clause has been added, but the report is still displaying full results. Any ideas?? Thanks
Hi Michele. I have found that using DATA…REFRESH does not re-run the report but instead returns the data in your report to what was in the data cube attached to it originally. I have even seen this behaviour when the report is linked to another universe & then refreshed.
We do something here which I think will help you. I first create a standard report using a user id which does not have any row restrictions so that all data are returned in my data cube. I then set the report to REFRESH UPON OPENING (under Tools…options… I think). The report is then saved and sent using SEND TO USERS to a user that has a bogus row restriction. What I mean by bogus is say you are restricting on sales rep area and valid areas are ‘A’ - ‘Q’. The user with the bogus row restriction would have it set up as WHERE SALES_REP_AREA IN (‘Z’). I then log on as the user with the bogus row restriction. The report refreshes and an empty report is returned to me. Then, while still logged on as the bogus user, I send the report to the sales reps. Each rep who opens the report will see the report being refreshed. At this time their individual row restrictions will be applied so reps in are A will see only area A, etc. Hope this helps.
Crystal Golding
Senior Systems Analyst
Management Information Section
University of Queensland
Brisbane Australia 4072
E-mail: c.golding@mailbox.uq.edu.au
Phone: +61 7 336 57289
Fax: +61 7 336 58202
Just a few notes on the side that might give you a better understanding of what happened. We are not on 4.1.3 yet, so things might be a little different in that version.
now tried to login as the user I have restricted and refresh a
standard
report
1: Using refresh data doesn’t give you (automatically) a re-generate of the query. Edit, run does.
2: When a change in the universe is detected on the repository, the universe is imported and refresh WILL first re-generate the query (But when your user doesn’t have edit query capabilities, this doesn’t happen and query will stay the same forever.)
3: Unfortunate enough a supervisor change to a universe for a particular user or group of users isn’t regarded a change in the universe. Only a universe export is.
4: When you log in first time as user A (capable of seeing everything) the universe gets imported. When you now log in on the same PC as user B (the restricted user), it will not automatically re-import the universe just because the restrictions of user A are different from user B.
So what should help is deleting the universe copy and then logging on to BO as the restricted user.
Hope this clarifies your problem,
Marianne Wagt-van Loenen
IDETA
The Netherlands