Answer
Check the field's own access configuration before assuming it's a data problem — a custom field can have narrower visibility than the page it sits on, which looks identical to missing data from the affected user's point of view.
Work through these checks
- Compare the same record and field with an affected normal user and a permitted normal user in the same environment. Record the page, context, and underlying field identity.
- Check whether the field is a stored value or a reference/derived value. An inaccessible referenced record can produce a different symptom from an empty stored value.
- Review applicable field/page grants and the data scope of the referenced source. Confirm the intended company/site access before changing permissions.
- Repeat allowed and denied cases after the smallest approved change. Verify save/reopen behavior where the field is writable and ensure unrelated records remain restricted.