Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Security Role Access Error RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have a 2 groups of users that access On Premise CRM 2011 CASE entity. The first group has read write access to the entity and the second group a read only access (business unit level). The first group can access the entity form and update records without any issue. The second group however are getting the following error message:

    "There was an error with this filed's customized event.

    Field: window

    Event: onload"

    I checked the entity and I don't have any onload events or any code scripts on this particular form. also no field with the name "window"

    The view only user group also receives the same error message when they try to create an Activity from the Case form.

    I tried changing some access rights for the view only (second group) users but they are still receiving this error when they select a CASE record and open the entity form. Unfortunately the error message is meaningless and there are no clear details on what should be changed in the security role to allow them to view the record without receiving an error message.

    I appreciate any suggestion that may help us resolve this issue. I am enclosing the error screen.

    Wednesday, November 6, 2013 10:43 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    the best approach is using CRM trace log view to see the log,  well, I could not directly define the problem right now, however, since it work for your first group, then my solution is try to replicate the same privileges as your first group to your second one, try to identify the issues, and try to minimize priviliges as expected. it may helps,

    cheers,

    MJ

    • Marked as answer by HS2010 Thursday, November 7, 2013 8:57 PM
    Wednesday, November 6, 2013 10:53 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    the best approach is using CRM trace log view to see the log,  well, I could not directly define the problem right now, however, since it work for your first group, then my solution is try to replicate the same privileges as your first group to your second one, try to identify the issues, and try to minimize priviliges as expected. it may helps,

    cheers,

    MJ

    • Marked as answer by HS2010 Thursday, November 7, 2013 8:57 PM
    Wednesday, November 6, 2013 10:53 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    As Marshall suggested copying the first group's role and reducing the privileges can help in solving the issue. We had this issue when the user did not have read privilege on web resource but had read for the entity. It is always better to copy an existing role and remove the unwanted entity privileges.

    If my response helps you in finding your answer then please click 'Mark as Answer' and 'Vote as Helpful'

    Wednesday, November 6, 2013 11:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you Marshal and Mamatha. I strated from the security role of the first group that has read/write access and was able to minimize some privilages to create the second group security role (read only) and that solved the issue, although there is no logical relationship between what was changed and the previous error.

    Thanks for your input.

    Thursday, November 7, 2013 9:01 PM