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.

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.

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.

Hi Experts,
I am trying to solve this challenge but not able to solve because of salesfore license issue. Salesforce only allows 2 'Salesfoce' license for DE. Is there a way to solve this challenge? Please help.

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'.