Ask Search:
Mark SmitheyMark Smithey 

Why would a new Lightning user be unable to access cases via a related list of an account when another user with identical role and profile can access normally?

We have several users who, when attempting to view a case from the account page in the service console, gets the following error:  INVALID_FIELD: AccountId = '0011I00000Jkv4mQAB' OR ContactId = '0031I00000DHGhTQAX' ^ ERROR at Row:1:Column:347 No such column 'ContactId' on entity 'Case'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.
I then have 2 other users that have no issue.  I then took one of the 3 failures and gave the exact same access as the successful users and that user still has the same problem.  
 
Best Answer chosen by Mark Smithey
Mark SmitheyMark Smithey
Share settings should have it all covered and the user can access all records in Classic.  This issue did not come up until we brought up Lighting.
 

All Answers

Nick SauerNick Sauer
Trying to access same records?  Sharing settings same between the two?  Any debug logs on the error other than what you have shown?
Mark SmitheyMark Smithey
Share settings should have it all covered and the user can access all records in Classic.  This issue did not come up until we brought up Lighting.
 
Mark SmitheyMark Smithey
Share settings should have it all covered and the user can access all records in Classic.  This issue did not come up until we brought up Lighting.
 
This was selected as the best answer
Mark SmitheyMark Smithey
Apparently is a bug in Lightning Experience. It happens for Person Accounts, when the running user doesn’t have the read right on the Contact Name field on the Case.
 
https://success.salesforce.com/issues_view?id=a1p3A000000EAgaQAG

Not an issue in Classic but this is something to watch for in Lightning.