I have a list view for a custom object (the object does not have Record Types) that users, and even System Administrators, cannot inline edit the new custom fields that I just added (lookup to User, lookup to Contact, and a Pick List field.) There are no lookup filters on the fields, nor filters on the List View other than by Owner: All. The Users can however edit those same fields in a detail record view (which is a Lightning Record Page that I recently converted to Dynamic Forms and added these new fields), so we know they have CRED and Field Level Security (FLS). They can edit the Name field, and while they don't have FLS for any other fields, Sys Admins can inline edit some other custom fields, but not these new fields. Sharing Setting for the object is Public Read-Only, FLS for the custom fields are Visible/Read-Only, and a Permission Set gives Edit CRED to specific users (of course Sys Admins have Modify All Data). The List View, Object, Custom Fields, Permission Set, and Profile Settings For Included Components were deployed from a Developer Sandbox to a Full Sandbox and then to the Production org. The inline editing works beautifully in the Developer Sandbox and Full Sandbox for, but the particular fields that the users need to edit have lock symbols next to the values in the list view, and also for Sys Admins. I have compared all settings and configurations across the orgs, but do not see any difference.
Thanks in advance for any help.
Are the fields you deployed on the page layout in production?
Fields that aren't on a page layout can't be inline edited. I think that might be the only thing that's missing here. If you deployed the fields but didn't add them to page layouts yet, that might be your issue.
