16 Comments »

David Berman said:
Re: “You do not have permission to view this record or this record has been deleted”
Either the user clicking on the drilldown is not on the team of the target record (i.e. their position isn’t part of it) –> record access issue – valid error
or
the target record the user is drilling down to has been deleted, so there’s nothing to drill to (e.g. Opportunities list view, user tries to drill down on the account tied to the oppty, but that account was deleted by somebody else).
Cheers,
David
# 9 December 2009 at 11:08 pm

Ashish Kumar (author) said:
Thanks David for guidance.
# 9 December 2009 at 11:30 pm

Andrey Borzov said:
Some details to David’s explanation. Normally this happens when destination record is not available to a user because of access issues (not a part of a sales team) or because of additional filtering (search spec) on BC or Applet level .
I will try to give a functional explanation based on OOTB Siebel 8 Financial.
Example: Let’s say a User has “My Contacts” view, “All Contacts” view, “Contact’s Call Reports” view and “My Call Reports” view but not “All Call Reports” view (it’s not technical names of views).
1. User goes to All Contacts and selects not his contact (he is not in a Sales/Coverage Team).
2. User goes to Contact’s Call Reports view.
3. From that view User tries to drilldown into a call report of that contact. Most likely the user will not be in MVF Employees of that Call Report.
Siebel will check views and BC’s view modes available to a user and will apply maximum available visibility “on top” of destination view (“Detailed Call Report” view). In our example it will be “My Call Reports” and Sales Rep view mode which checks positions(!) in Employees field.
So, our User will get an error instead of “Detailed Call Report” view.
Easiest way to fix is to override visibility for every drilldown (for every source applet) to “All”, or to give “All..” views to users.
Search specifications on BC or Applet levels cal also filter out some destination records having mentioned error as a result.
For example:FINxxx Call Report BC (sorry, don’t remember exact name) has SearchSpec checking Private Flag field for Y or N. But if this field is NULL (normally happens for migrated from legacy systems historical CRs or created from migrated activities) than this record will be dropped out in both cases. If a user will try to drilldown into this Call Report the error message will appear.
# 10 December 2009 at 6:56 am

Andrey Borzov said:
Correction for last chapter:
For example: FINxxx Call Report BC (sorry, don’t remember exact name) has SearchSpec checking Private Flag field for Y or N. But if this field is NULL (normally happens for migrated from legacy systems historical CRs or created from migrated activities) than this record will be dropped out in both cases. If a user will try to drilldown into this Call Report the error message will appear.
# 10 December 2009 at 7:00 am

Ashish Kumar (author) said:
Andrey corrections has been incorporated in your previous reply as bold italic font.
Thanks.
# 10 December 2009 at 8:47 am

Ashish Kumar (author) said:
The errors has been well explained by Andrey and David both but while dealing with drilldown related issues firstly you must ensure that whether the destination view has been registered with Use’s responsibility or not. This will be the first check point and if this is okay then you can proceed with the diagnosis suggested by Andrey and David.
# 10 December 2009 at 10:36 am

Rahul Khullar said:
Two main reasons:
1) Appropriate views not assigned to specific responsibilities
2) Filters used at Applet or BC level (Search Specifications) which are restricting the views after drilldown
# 10 December 2009 at 11:23 am

David said:
I just wanted to add a small clarification – usually, when the user doesn’t have access (via responsibility) to the target/destination view, then the drill-down from the source view will be inactive (i.e. there won’t be a hyperlink). This means the user cannot drill down to a view that isn’t part of the user’s list of responsibilities.
# 11 December 2009 at 10:01 am

Ashish Kumar (author) said:
Yes, You are right David.
If the User doesn’t have the destination view in his list of responsibility then he wont be able to see drilldown hyperlink in the field which has above said destination view defined. The field will not have Hyperlink.
I have seen lot many issues logged as the user is not able to see hyperlink in the drilldown field. which is just because of destination view not registered with an user responsibility.
# 11 December 2009 at 12:41 pm

Hua said:
I used to see the second error. The root cause is user don’t have privilege to access the target record in destination view. We fixed it by change the property in drill down definition.
# 3 January 2010 at 12:13 pm

krishna said:
Also there could be a possibility that the record is visible in the All view but not in the My view of the destination view. Hence when the user drill down, it throws error since there is no such record in My view.
# 13 January 2010 at 10:34 pm

Uma said:
Hi Ashish,
I have a issue on drill down i will post it tomorrow with exact error message, It is more of an issue with DB layer but having tough time tweeking it….
Regards,
Uma
# 21 January 2010 at 8:28 am

Ashish Kumar (author) said:
Please share the error Uma. Please also provide the screenshot of error to contact@siebeloracle.com
# 21 January 2010 at 1:03 pm

Satyesh S said:
Error : “You do not have permission to view this record or this record has been deleted”
In my case i encountered the above error when one of the user who created a record was deleted from the S_USER table. Now since the user who created the record itself is not present in the DB, There is no way any one can view this record.
Even if the user is recreated it will be created with a different row_id in S_USER table and thus will not be able to view this record.
# 17 June 2010 at 9:00 am

Reva said:
Is it possible to nevigate to the view but there are no records to display in the applet . in short it would nevigate to the view, but the applet would have 0 records to display?
# 15 November 2011 at 1:56 pm

Apeksha Bameta said:
Use default PDQ for blank output.
# 15 November 2011 at 2:30 pm

Leave your response!

Our Stats

hit counter

Author Spotlight

Ashish Kr. Bameta

Join us in Facebook !!!!

Training Partner

Advertisement

Advertisement