locked
Principal user "SYSTEM" is missing prvReadSLA privilege RRS feed

  • Question

  • Hi,

    I had a .NET web application connected to CRM 2011 and now, after migrate to CRM 2013 and while testing this application I get an exception when trying to update an Incident record with:

    XrmContext.Update(theCase);

    being XrmContext (created by CRMsvcutil.exe)

    The exception I get is {"Principal user (Id=b9d717c3-1049-4834-80ea-51980850e66a, type=8) is missing prvReadSLA privilege (Id=9a06070d-af1d-4971-90c9-f64487eeeaac)"

    User with that ID is "SYSTEM" account.

    I'm able to create an Incident or any other custom entities.

    I'm connecting the web app to CRM using a custom account that is not the SYSTEM user.

    I've given the user which impersonate and the user running the app administrator security role with same results.

    Why to perform this operation is asking for that permission?

    Could be due to the new relationship with Case - SLA in CRM 2013?


    • Edited by RDevelopment Wednesday, October 15, 2014 1:14 PM
    Tuesday, October 14, 2014 12:03 PM

All replies

  • Makes sense it would be the SLA relationship. There is a field called slainvokedid.

    How are you creating theCase object? Are you retrieving it from CRM or are you creating it as new? If you are retrieving it using a service call are you returning all fields or are you only returning specific fields?

    Tuesday, October 14, 2014 12:23 PM
  • Yes, I'm retrieving the Case, but only two fields of it, and after when trying to update I return with one or both fields.

    Tuesday, October 14, 2014 1:25 PM