Loading

Education Cloud object returns "Entity is not api accessible" — how to distinguish license gating from API version gating and resolve permission-state drift

Publiseringsdato: Jul 29, 2026
Beskrivelse

The error message "Access to entity '[Object]' denied: Entity: [Object] is not api accessible" is returned by the Salesforce platform when the running user or the executing code cannot access the named object. In Education Cloud environments, this error has two distinct causes that are commonly confused:


Cause 1 — License or Permission Gating (access error): The running user does not have the required Permission Set License (PSL) or permission set for the object. Education Cloud objects such as EducationalInfoRequest require both an Education Cloud PSL (e.g., Education Cloud Full Access or Education Cloud Limited Access) and a corresponding permission set. If either is missing, the API returns the "not api accessible" error regardless of Object permissions or profile settings. This is the more common cause in sandbox environments, where PSL assignments are not always carried over from production after a refresh.


Cause 2 — Apex API Version Gating (version error): An Apex class or trigger executing in the context of the API call is saved at an API version lower than the version in which the object was introduced. The Apex runtime performs a dynamic describe of the object at the class's version ceiling; if the object did not exist at that version, the describe fails. For example, EducationalInfoRequest was introduced at API version 57.0. An Apex class saved at version 56.0 cannot see it, and any trigger that invokes that class will throw the same error — even if the user has full permissions.


Disambiguation — per-API-version count probe: To determine which cause applies, run a direct API call (e.g., a SOQL query against the object) as the affected integration user, outside any Apex context. If the query succeeds, the user-level access is intact and the cause is Apex API version gating. If the query fails with the same error, the cause is license or permission gating.

Løsning

For license/permission gating:

  1. In the affected org, go to Setup → Users and open the integration user record.
  2. Check Permission Set License Assignments — confirm an Education Cloud PSL (Full Access or Limited Access) is assigned.
  3. Check Permission Set Assignments — confirm the corresponding Education Cloud permission set is assigned.
  4. Compare with the equivalent user in production. If production has assignments that sandbox does not, re-assign them in sandbox.
  5. Re-run the integration and confirm the error is resolved.

For Apex API version gating:

  1. Identify the Apex class(es) in the trigger framework that perform dynamic describes or that execute in the call chain before the failing operation.
  2. In the Developer Console or VS Code, open each class and check its API version (Setup → Apex Classes → class detail, or <apiVersion> in the metadata XML).
  3. Update the API version to 57.0 or higher (the version in which EducationalInfoRequest was introduced). Using the current API version (e.g., 66.0) is recommended to ensure compatibility with future objects.
  4. This is a metadata-only change — no code modifications are required.
  5. Deploy the updated class and re-run the integration.
Flere ressurser

Related case: 473617653. This case involved an Education Cloud integration in a Summer '26 Preview sandbox (USA772S). The initial hypothesis was license-gating (PSL missing after sandbox refresh), which was correct for the first diagnostic phase. After the customer confirmed PSL parity with production, the root cause was re-examined and found to be Apex API version gating: the TriggerBase class was saved at API version 56.0, below the 57.0 threshold for EducationalInfoRequest. The fix was bumping TriggerBase to API version 66.0 — no code changes. The "not api accessible" vs "is not supported" distinction: "not api accessible" is a license/permission or version-ceiling error; "is not supported" is an API-version retirement error (object removed from that version's schema).

Knowledge-artikkelnummer

005387167

 
Laster
Salesforce Help | Article