This issue occurs because Apsona displays fields based on their Salesforce field labels, not their API names. In this case, the standard Phone field was not missing—it had been relabeled in Salesforce as “Business Phone,” which is why it did not appear under the expected name in Apsona.
Even though the field was visible in Salesforce, permissions were correctly configured, and cache was cleared, the discrepancy was due to the customized field label. Apsona correctly reflected this label, causing confusion when searching for the original “Phone” field name.
The resolution is to use the “Business Phone” field in the report, as it represents the standard Phone field in that org.
If a field appears to be missing in Apsona, always check whether it has been relabeled in Salesforce, since field label customization is a common cause of such issues.