Related List Item
A Related List Item is a single record shown as one row inside a Salesforce related list.
Definition
A Related List Item is a single record shown as one row inside a Salesforce related list. It represents one related record, such as a contact, a case, or a custom object record, that is connected to the parent record currently on screen. Each row carries a link to open the underlying record, a set of columns that display chosen fields, and an actions menu for that record. The related list is the container; the related list item is one entry within it. The connection comes from a lookup or master-detail relationship between the two objects.
How a related list item works on a record page
One row, one related record
A related list groups records that share a relationship with the record you are viewing. An Account page, for example, can show related Contacts, Opportunities, Cases, and custom records. Inside that list, every line you see is a related list item, and each one stands for exactly one related record. The columns on the row display fields from that record, like a name, a status, or a date, so you can scan many records without opening each one. The row also holds a link that opens the full related record when you click it. Salesforce builds these rows from the relationship field that ties the child object back to the parent. When a Contact has an Account lookup pointing at the Account you are on, that Contact surfaces as a related list item on the Account. The list is the container and the item is the single entry inside it. Knowing this distinction matters when you talk about layout, troubleshooting, or automation. A request to "add a column to the related list" changes what every item shows. A request to "delete a related list item" removes one related record from the relationship, not the list itself.
What the columns on each item show
The fields that appear on a related list item are not random. An admin chooses them when configuring the related list, either on the page layout or in the Lightning App Builder. You can include up to 10 fields per related list, set the order they appear in, and pick the sort order for the records. By default, the standard related list component in Lightning Experience shows up to four fields on each item. To show more than four, you edit the related list component in the Lightning App Builder and choose Enhanced List as the related list type. That lets each item display the full set of configured columns, up to the 10-field limit. The columns are the same across every item in a given list, so the layout you design applies to all rows at once. This is why thoughtful field selection pays off. Picking the two or three fields a user actually needs turns a wall of rows into something scannable. Adding rarely used fields just makes each related list item wider and harder to read at a glance.
Acting on a single item
A related list item is interactive, not just a display row. Clicking the primary link opens the related record in full. Next to each row sits a pull-down actions menu that holds record-specific actions, such as Edit, Delete, or a custom Quick Action defined for that object. These row-level actions let a user work on one related record without leaving the parent page. Some related lists also support mass actions. You select several items using the checkboxes, then apply an action to all of them at once, which is handy for updating or reassigning a batch of child records. Inline editing is available on many related lists too, so a user can change a field value directly on the row and save without opening the record. The set of actions on each item depends on the object, the user's permissions, and how the admin configured the list. A user who lacks edit access on the child object sees a read-only item with no Edit action. This per-row action model keeps common work close to where the data lives.
How many items show before View All
A related list does not always show every related item at once. On a Lightning record page, the number of items visible depends on where the related list card sits. In a wide region, each card displays up to six records. In a narrow region, the card shows up to three. The card includes a View All link that opens the full related list, where the rest of the items appear. The expanded view is where the related list item becomes most powerful. Users can apply multi-column sorting, add quick filters to narrow the rows down, and work through a much longer set of records. Quick filters are not supported in every related list, so the option may not always appear. Related list hover links, enabled in the user interface settings, give another fast path. A user hovers over a link at the top of the page and a pane shows that list's items in an overlay, where they can view and act on records without scrolling. The point is that the items you see first are a preview, and the full set is one click away.
Dynamic related lists and per-item filtering
Standard related lists show every child record that matches the relationship. Dynamic related lists go further. Using the Dynamic Related List - Single component in the Lightning App Builder, an admin can choose the columns, sort order, and actions for a list directly in the builder rather than on the page layout. The bigger gain is filtering. You can apply a filter so the list only shows the related list items that matter, like open Cases or Opportunities above a certain amount. You can also give the list a custom name that tells users exactly what they are looking at. This means the same parent record can carry two lists built on the same child object, each filtered differently, each made of a focused set of items. A Cases list might split into "Open Cases" and "Escalated Cases" on the same Account. Each related list item still represents one record, but the set of items in view is curated. Dynamic related lists are the modern way to control which items appear, and they replace a lot of the rigidity that came with layout-only related lists.
Troubleshooting items that do not appear
When an expected related list item is missing, the cause is usually access or configuration rather than a bug. Field-level security and object permissions decide whether a user can see a child record at all. If a profile lacks Read access on the child object, the related list can come up empty or fail to render, even though the records exist. The relationship field is the other common culprit. A related list item only appears when the child record's lookup or master-detail field points at the parent you are viewing. If that field is blank or points elsewhere, the record will not surface on this parent. Layout placement matters too. A related list has to be added to the page layout or the Lightning record page before any of its items can show, and a list that was never placed simply will not be there. Sharing rules add a final layer. A user might have object access yet still not see a specific item because the underlying record is not shared with them. Checking permissions, the relationship field value, the layout, and sharing in that order resolves most missing-item reports quickly.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Related List Item.
Hands-on resources to go deeper on Related List Item.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does a single Related List Item represent in a Salesforce related list?
Q2. Which fields appear on a given Related List Item row?
Q3. What typically happens when a user clicks the name on a Related List Item?
Discussion
Loading discussion…