Power Platform Community Forum Thread Details

I am developing a Power Pages portal and facing an issue retrieving records from a custom table (mkd_planning) using the Portal Web API. By design, users should only see "Plannings" related to a "Session" they have signed up for.

Data Model & Logic:
The relationship chain is a bit complex. Here is the flow from the User to the Planning records:

Contact: The logged-in system user.
Learner (mkd_learner): Related to Contact via mkd_linked_contact.
Submission (mkd_submission): This is the junction table representing a signup. It connects a Learner (via mkd_linked_learner) to a Session (via mkd_linked_session).
Session (mkd_session): The parent event.
Planning (mkd_planning): The child records I need to fetch. These are related to the Session via lookup mkd_assignedsession.

Current Status:
The Web API works perfectly for the first few levels of this chain.

GET /_api/mkd_learners $\to$ Returns only the logged-in user's learner record (Success).
GET /_api/mkd_submissions $\to$ Returns only the submission for that learner (Success).
GET /_api/mkd_sessions $\to$ Returns only the session linked to that submission (Success).

The Problem:
When I try to go one step deeper to fetch the plannings (GET /_api/mkd_plannings), I get this error:

{
  "error": {
    "code": "9004010D",
    "message": "Common Data Service error occurred.",
    "cdscode": "0x80040216",
    "innererror": {
      "code": "0x80040216",
      "message": "entityRelationshipRole for given navigation property not found"
    }
  }
}

My Table Permission Configuration:
I am using a chain of Child Table Permissions in the Portal Management App. All 4 permissions are assigned to the same Web Role ("Authenticated Users").

Permission A (Root): mkd_learner
- Access Type: Contact Scope (via mkd_linked_contact).
- Status: Works.
Permission B: mkd_submission
- Access Type: Parent (Parent Perm: Permission A).
- Status: Works.
Permission C: mkd_session
- Access Type: Parent (Parent Perm: Permission B).
- Relationship: mkd_submission_mkd_session (Session is looked up on Submission).
- Status: Works.
Permission D: mkd_planning
- Access Type: Parent (Parent Perm: Permission C).
- Relationship Selected: mkd_planning_AssignedSession_mkd_session
- Status: Fails with 0x80040216.

Troubleshooting Steps Taken:

Tested Data Existence: I temporarily changed Permission D (mkd_planning) to Global access. The API immediately returned the records successfully. This confirms the API is enabled, the Entity Set Name is correct, and the data exists.
Verified Schema: I checked the Solution in Power Apps. The N:1 relationship from Planning to Session is definitely named mkd_planning_AssignedSession_mkd_session.
Verified Web Roles: Confirmed all four permissions belong to the exact same Web Role.

Question:
Why does the Power Pages Web API fail to resolve the relationship role (0x80040216) specifically at the 4th level of this hierarchy? Is there a limit to how deep permissions can cascade for the Web API, or is there a specific relationship naming convention I am missing?

Categories:

Customize & extend

Power Apps portals

Security