Apsona Grids can only access fields from the starting object and its direct parent objects. Objects beyond that (grandparent, great-grandparent, or child/grandchild objects) are not automatically available. If a field or object cannot be seen—or you encounter errors like “Can’t find field…”—it can be due to several reasons. Use the steps below to identify and resolve the issue:
Troubleshooting Steps:
Clear Apsona Cache
Each user must clear their own Apsona cache to refresh object/field visibility after Salesforce changes. Cache is browser-based and unique per user/browser.
Admin Verification
If you're an admin, log in as the affected user.
Check Apsona Configuration
Ensure the object and fields are included in the user’s Apsona Configuration.
If you make changes, the user must clear the cache again.
Check Salesforce Field-Level Access
If the field is not visible in Salesforce either, review the user’s Profile or Permission Sets for object/field access.
Lookup Field Dependency
If the missing field references another object (e.g., Opportunity → Primary Campaign Source), the referenced object must be included in the user’s Apsona Configuration.
New Salesforce Cloud Fields
Some new fields in industry clouds (Health Cloud, Education Cloud, NPSP, etc.) require the latest Salesforce API version.
If Apsona has not yet updated to that API version, such fields may temporarily be unavailable.
Deprecated Managed Package Fields
Some managed packages retire fields. They still appear in Salesforce but are removed from the API.
Affinaquest Users (If Applicable)
When Affinaquest is upgraded, users may lose access to objects/fields until the updated permission sets are applied.
Confirm the correct objects/fields are included in Apsona Configurations.