When customizing Lightning Record Pages (Flexipages) in Salesforce Education Cloud, you may find that a child standard object is not available in the Lightning App Builder component picker. Even though a valid lookup relationship exists between the parent and child objects, the child does not appear as an option when dragging a Related List or Related List - Single component onto the canvas.
Common reports from administrators include:
"I cannot add the Individual Application related list to the Account page, even though the Billing Account Number lookup is configured on the Individual Application object."
Product: Salesforce Education Cloud
Edition: Lightning Experience (Enterprise, Performance, Unlimited, and Developer Editions)
Impacted Role: System Administrators or developers with customization rights to Lightning Pages and Page Layouts.
Excluded Issues: This article does not cover polymorphic field failures on ApplicationDecision objects, which is a separate schema limitation handled in a dedicated article.
The Lightning App Builder's Related List components dynamically query the parent object's standard page layouts to determine which related child lists are available to display. If a child object is missing from the Lightning App Builder picker, it must first be exposed on the classic page layout.
Work through the following steps to resolve this behavior:
Root Cause: Lightning App Builder reads the master metadata schema from the Classic Page Layout engine. If the child related list has not been dragged onto the classic page layout assigned to your profile, the App Builder's component properties pane will hide it.
Navigate to Setup > Object Manager.
Open the PARENT object that hosts the record page you are trying to edit:
Example 1: Program Term Application Timeline (API: ProgramTermApplicationTimeline)
Example 2: Account (API: Account)
On the left sidebar, click Page Layouts and open the specific page layout assigned to your user profile.
In the upper palette, click Related Lists.
Drag the CHILD related list from the palette down into the Related Lists section of the page layout:
Example 1: Drag Education Institutional Offerings onto the Program Term Application Timeline page layout.
Example 2: Drag Individual Applications onto the Account page layout.
Click Save. If prompted with "Overwrite users' related list customizations?", click Yes to apply the layout globally.
Root Cause: If the classic page layout has been saved but the Related List component still does not offer the child object, the relationship name may be missing from the lookup field metadata.
Go to Setup > Object Manager and select the CHILD object (e.g., Education Institutional Offering or Individual Application).
Click Fields & Relationships and select the lookup field pointing to the parent object.
Verify that the Data Type is indeed Lookup Relationship and that the Related To property points to your target Parent Object.
Check the Child Relationship Name field. If this value is blank, click Edit, define a clear API relationship name (e.g., EducationInstitutionalOfferings), and save.
Go back to Setup > Lightning App Builder and open your parent record page.
Search for the Related List - Single component on the left-side standard components pane and drag it onto your canvas.
In the property editor on the right, select your child object from the Related List dropdown menu.
Click Save, then click Activate to deploy the updated page to your profiles.
Navigate to your app in Education Cloud and open a parent record (such as a specific Program Term Application Timeline record).
Confirm that the child related list (such as Education Institutional Offerings) now appears on the page.
Create a test child record under this parent to ensure that the related list populates and displays the records correctly.
005389149

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.