You need to sign in to do that
Don't have an account?
Trailhead Module Data Security Controlling Access to Fields Error Message: The 'Basic Account User' profile did not have the appropriate object and field-level security for the Account object
I am trying to complete the Trailhead Module "Data Security: Controlling Access to Fields"
Create a Profile and Permission Set to properly handle field access
The Marketing Coordinator and Account Manager both require access to view and update Account Records, but only the Account Manager should be able to see and edit certain fields. Specifically, only the Account Manager should be able to see and edit the Rating field. The Marketing Coordinator should not be able to see or edit the Rating field. Create one profile and one permission set with the appropriate field-level security to solve for this use case.The profile must be named 'Basic Account User' and result in an API name of 'Basic_Account_User'. It should use the 'Salesforce' user license type.
The permission set must be named ‘Account Rating’ and result in an API name of 'Account_Rating'.
This is driving me absolutely insane.
I created a custom profile named Basic Account User, it is Read on the Account Object and the Rating field is unchecked for both Read and Edit.
I created a permission set named Account Rating, it is Read & Edit on the Account Object and the Rating field is checked for both Read & Edit.
I have both the profile and permission set assigned to the other user in my Dev Org. I logged in as this user and the permission set is functioning as expected. With the permission set he can see and edit the rating field, without the permission set he can't see it at all.
Yet I keep receiving the "The 'Basic Account User' profile did not have the appropriate object and field-level security for the Account object" error message.
What am I missing? I have tried every conceivable combination.
Create a Profile and Permission Set to properly handle field access
The Marketing Coordinator and Account Manager both require access to view and update Account Records, but only the Account Manager should be able to see and edit certain fields. Specifically, only the Account Manager should be able to see and edit the Rating field. The Marketing Coordinator should not be able to see or edit the Rating field. Create one profile and one permission set with the appropriate field-level security to solve for this use case.The profile must be named 'Basic Account User' and result in an API name of 'Basic_Account_User'. It should use the 'Salesforce' user license type.
The permission set must be named ‘Account Rating’ and result in an API name of 'Account_Rating'.
This is driving me absolutely insane.
I created a custom profile named Basic Account User, it is Read on the Account Object and the Rating field is unchecked for both Read and Edit.
I created a permission set named Account Rating, it is Read & Edit on the Account Object and the Rating field is checked for both Read & Edit.
I have both the profile and permission set assigned to the other user in my Dev Org. I logged in as this user and the permission set is functioning as expected. With the permission set he can see and edit the rating field, without the permission set he can't see it at all.
Yet I keep receiving the "The 'Basic Account User' profile did not have the appropriate object and field-level security for the Account object" error message.
What am I missing? I have tried every conceivable combination.
This is what I did for the challenge and it worked.
I created a new profile named 'Basic Account User' cloned from the 'Standard User' profile.
I then set the field level security for Accounts -> Rating as below:
Unchecked it for all the other profiles.
Thanks,
Shyama
All Answers
This is what I did for the challenge and it worked.
I created a new profile named 'Basic Account User' cloned from the 'Standard User' profile.
I then set the field level security for Accounts -> Rating as below:
Unchecked it for all the other profiles.
Thanks,
Shyama
They really need to reword the instructions and specify whether the Marketing Coordinator & Account Manager would be using the same profile or not.
YEEEEEEEAAAAARRRRRRRRRGGGGGGGGGHHHHHHHHHH!!!!!!!!!!!
I finally got it after unchecking every. Single. One. Of. Those. Field Permissions. In. The. Account Ratng. Permission Set.
I say it again...YEEEEEEEEEEAAAAARRRRGHHHHHHHHH!!!!!!!!!!
What's worse is that I am on a plane on the way to Dreamforce, so I can't bloody well go off in this enclosed space...you woud see the story tomorrow of someone being taken off the plane in Salt Lake City. Observers only heard the following words....Trailhead...field level security....nnnnggggggg...some on the plane seemed to know what he was saying, but declined to comment; reason being is that the first rule of Trailhead is...
You don't talk about Trailhead...
Two team members need to view and update Accounts, but only one should be able to see and edit the Rating field. Create one profile and one permission set with field level security to solve for this use case.
But that does not help, I think this whole item needs to be reworked... I was flying along until this one and I really think I might skip this segment as it is really just confusing me and wasting my time...
I don't understand where is the "Field level security for Accounts -> Rating" ? I would appreciate the step by step so that I can move past this.
1. Create a new profile named 'Basic Account User' cloned from the 'Standard User' profile.
2. Goto Customize/Accounts/Fields, click Rating (in Field Label column), click Set Field-Level Security button, and
set the field level security for Accounts -> Rating as below (only check it for Basic Account User, and Unchecked it for all the other profiles)
3. Create a permission set named 'Account Rating', and go to object settings, click Accounts, click Edit, check Read and Edit in Object Permissions, check Read and Edit for Rating Field, click Save.
Thank you very much!
I also went to Manage Users > Profiles > Basic Account User > Edit and unchecked Read and Edit for the Ratings field. I’m not sure if this was necessary with the other instructions, but it seemed to work.
I think Katherine Cheng 7 wrote very clear instructions. That was a big help.
logged into a 2nd developer account I have
follow Katherine Cheng's steps
And it worked!
Now my rating field is a mess in the main developer org but hey ho, I hope I never have to use it again!
set the field level security for Accounts -> Rating as below (only check it for Basic Account User, and Unchecked it for all the other profiles)
Can someone please state the step by step procedure so that to complete the challenge (Control Access to Fields)
For SETTING FIELD PERMISSION/SECURITY FOR PARTICULAR USER
2. Setup > select object ‘Account’ > field and relationship > click field ‘Rating’ > clcik ‘Set Field level security’ >