If an Apsona report works for one user but fails for another with an error such as "Can't find field Opportunity.CnP_Paas__C_P_Recurring__c", the issue is typically related to user-specific field access, Apsona Configuration, or stale metadata.
First, verify that the affected user has Read access to the referenced Salesforce field. If the field belongs to a managed package, also verify that any required permission sets are assigned. Next, check the user's Apsona Configuration to ensure that the Opportunity object and the referenced field are visible.
If the permissions and configuration are correct, clear the affected user's Apsona cache and retest the report. Apsona stores object and field metadata locally, and outdated metadata can result in missing-field SOQL errors.
When troubleshooting user-specific report errors, always verify that:
The affected user has Read access to the referenced Salesforce field.
The object and field are Visible in the user's Apsona Configuration.
Required permission sets are assigned, if applicable.
The user's Apsona cache is cleared after making permission or configuration changes.
These checks help resolve missing-field errors when the same Apsona report works correctly for other users.