Skip to main content
I have a process that generates an email when a new Case is created. Some of the fields from the Case that are in the email are formula fields that refer to the related Account object. When I create a case when logged in from my admin account, the fields show up in the case correctly and are in the email correctly. When I create a case from a standard user profile, the formula fields show up as zeros in the Case for the standard user and they do not end up in the email. The formula fields are visible to both profiles and there is no special security on the fields. If anyone can explain why the standard users can't see the fields, I would really appreciate it. 

 

On a possibly related note, when a standard user creates a Case from an Account object, it does not show up on the list of related case objects for that Account. If I create a Case for an Account as an admin profile, it does show up related to the account. 
4 respuestas
  1. 30 oct 2018, 13:48

    Remember that permission sets grant additional abilities not contained in the profile - so their profile already provides access to the objects, that permission set is very likely giving them read and edit privileges on fields that are not included on their profile. Now that their field level security is extended through that permission set, everything works.

    I'm guessing if you look at the FLS for Accounts & Cases in the Permission set vs the standard user profile, you'll see what I mean.

0/9000