True. And the fact that you can see the restricted object when not opening on refresh is because the results are saved with the report. Only when you query the database via the universe with the restriction it will prompt you with an error.
But Myself only has set the restriction on the object and checking it in report. I dont want user to see the restricted object not even err while he refershing the document.
I want user to see only those object which is relevent to him.
I’m afraid that what you want is not possible (as far as I know). When you’ve created a report with an object that a user is not allowed to see this user will always see an error message when trying to refresh the report. You should either create different reports for different user groups or consider other options such as row-level security.
The scenario is like i have a drill on report.which is up to three level say A–>B–>C. so a user ‘X’ say is restricted for the object ‘A’ should not see the object A.for him the hierarchy should start from B–>C.
This is happening in one of my universe where the hierarchy is form the one table only i.e A,B,C all the three Object belong to one table only.
But in another universe where say these three object comming from three diffrent table is not happening.it shows that err message (wis:0002) or it will show the restricted object if i uncheck the option of “refresh on open”.
No, I’m sorry, I don’t. I would need to know more details. I’d advice you to investigate more closely how the restrictions are set up and in what they differ.