[SalesForce] Picklist field is disabled but profile and layout shows editible

I have a picklist field on a custom object that is disabled (grayed out) when I am editing a record on that custom object for a user in a profile that should have write access to that field.

I have verified the user's profile should have the ability to edit the field under "Field Accessibility" for that field (field-level security). I also have verified that the field is not "Read Only" on all of the object's page layouts.

This field is editable using the System Administrator profile.

Where/what else might I check?

Best Answer

The problem was due to the object having two record types with incorrectly configured picklist values. Record Type A had all of the picklist values. Record Type B had none. Not having any is an invalid state. When you try to remove all values from a picklist for a given record type, you'll get the following error:

At least one value must be selected

So, I believe this problem may have somehow been introduced via deployment to the test environment where this problem was found.

By adding the picklist values to Record Type B, the problem was solved.

Most interesting is the fact that regardless of which record type you were editing a record for, the picklist would be disabled, most likely caused by the invalid state mentioned above.

Related Solutions

[SalesForce] How to make Lead Status field read-only in a profile

I know you said no validation rules in your question, but based on your comments it seems like it's more of the aesthetics that's keeping you away from them. From personal experience, as long as you have a good error explanation that doesn't leave users confused, they have no problem with validation rules. In case you decide to go this route, here's a rule that may work for you.

AND($Profile.Name = 'Read-Only Profile', ISCHANGED(Lead_Status))

Error Message: Lead Status is a read-only field for users with the profile 'Read-Only Profile'

Hope this helps if you decide to use this.

[SalesForce] Permission Manage All X Depends On Permission Read All Y

I just ran into a very similar issue with Opportunity and a custom object that had a Master-Detail relationship back to Opportunity.

I was attempting to insert an ObjectPermissions record against Opportunity for a particular ParentId PermissionSet and got the following error:

Id permissionSetId = //... Some existing Permission Set gets looked up. 

// Note the omission of PermissionsViewAllRecords = true
ObjectPermissions opportunityObjectReadPermission = new ObjectPermissions(SobjectType = 'Opportunity',
                                                        PermissionsCreate = false,
                                                        PermissionsDelete = false,
                                                        PermissionsEdit = false,
                                                        PermissionsRead = true
                                                    );
opportunityObjectReadPermission.ParentId = permissionSetId;
insert opportunityObjectReadPermission;

System.DmlException: Insert failed. First exception on row 0; first error: FIELD_INTEGRITY_EXCEPTION, Permission Read All ChildCustomObject__c depends on permission(s): Read All Opportunity: []

It turned out there was already an ObjectPermissions record for ChildCustomObject__c that had PermissionsViewAllRecords = true. For that to exist there was already a corresponding ObjectPermissions for Opportunity with the same view all records setting. That makes sense:

If you are going to allow the view all records permission on the detail object in a master-detail relationship you also need to grant it on the master object.

This is applicable to your deployment issue as well. You can't deploy permissions for the child/detail sObject without also deploying the required permissions to the master sObject.

Best Answer

Related Solutions

[SalesForce] How to make Lead Status field read-only in a profile

[SalesForce] Permission Manage All X Depends On Permission Read All Y

Related Topic