Related List Grids for Salesforce, Without Leaving the List

Written by

Peter Gascoyne

November 20, 2026

Related list grids for Salesforce with sidebar navigation, Grids 6.80 by RavenApps

Grids 6.80 upgrades Related Grids. Click the eye on any row to see everything related to that record, with the parent row pinned in sight, a lazy loading sidebar, and query-driven relationships that skip levels.

Summary

Grids 6.80 upgrades Related Grids in Salesforce. Click the eye on any row and see everything related to that record, without leaving the list you were working in. The selected record now sits at the top so you keep your context, a new sidebar switches between related grids, and both can be hidden when you want the space.

‍

Related grids are query-driven rather than lookup-driven, so they are not limited to direct child records. Skip levels, pull grandchild data, or show records that are related by meaning rather than by a lookup field. Available in Grids 6.80.

‍

A related grid opened from an Opportunity list view in Salesforce, showing the pinned record row, the related grid sidebar and Account Related Contacts
Clicking the eye on an Opportunity row opens its related grids, with the record itself pinned at the top and the sidebar on the left.

‍

Why did we build this?

A list view answers one question at a time. You look at twenty opportunities, you want to know what is happening on the third one, and the only way to find out is to leave the list.

‍

Then you come back, lose your scroll position, and do it again for the next one. Salesforce users have been absorbing that cost for so long that it stops registering as a cost.

‍

Related Grids removed the navigation. This release is about what happens after you click: keeping the context visible, making it fast to move between related objects, and letting the view scale to a record with a lot going on.

‍

What are related list grids?

Click the eye icon on any row in a grid, and a related view opens showing the records connected to that row, each in its own editable grid. The parent list stays where it was.

‍

From an Opportunity, for example:

  • Contacts and their roles
  • Open Tasks, Emails, Events and Calls
  • Products, Schedules and Files
  • Similar Opportunities, or everything else on the same parent account

‍

Each of those is a full grid, so the data is editable in place with the same column configuration, filters and permissions as anywhere else.

‍

Query-driven, not lookup-driven

This is the part that separates it from a standard related list, and it is worth dwelling on.

‍

A standard related list shows records with a lookup pointing at the record you are on. That is the whole model, which means anything two steps away is not available and anything related conceptually rather than structurally is not available either.

‍

Related grids are defined by a query. The relationship can skip a level, so from an Opportunity you can show the Account's other open Opportunities, or Contacts on the Account rather than only Opportunity Contact Roles. It can reach grandchild data, such as Schedules under Products. And it can be defined by meaning: "similar opportunities" is not a lookup, it is a query, and a query is something you can write.

‍

The record row stays in sight

New in this release: the selected record's own row appears at the top of the related view. It sounds small. In practice it is the difference between knowing which of four similar-looking opportunities you are editing Contacts for and guessing.

‍

It also makes the parent record editable from the same screen, so correcting a close date you noticed while looking at the Schedules does not send you anywhere.

‍

Sidebar navigation, with lazy loading

Moving between related grids now goes through a sidebar rather than a set of tabs that run out of room. The grids load as you open them rather than all at once, which is what makes a record with a dozen related views usable rather than slow.

‍

Lazy loading is the quiet part of this release. A related view that queries everything up front is pleasant with three grids and unusable with fifteen, and fifteen is where real orgs end up.

‍

Hide what you do not need

The sidebar and the record row can both be hidden to give the grid the full width, and your choice is remembered. People who work in one related grid all day get the space; people moving between them keep the navigation.

‍

Preview: adding related grids from the related view

Also in this release, as a preview, you can add related grids from inside the related view rather than going back to configuration. It is early and there is more to come, but the direction is the same as the rest of the product: the person using the data should be able to change the view without raising a request.

‍

How is this different from a standard related list?

  • Field count: a standard related list shows up to ten columns. A grid shows the columns you configure.
  • Editing: a related list is read-mostly, with an edit per record. A grid is editable inline, across many records, saved in one go.
  • Relationships: a related list follows one lookup. A related grid follows a query, including skipped levels and grandchild records.
  • Navigation: a related list lives on the record page, so you have to be on the record page. A related grid opens from the list view you were already in.
  • Context: the parent record's own values are now visible and editable alongside its children.

‍

Where teams use it

  • Pipeline reviews: run down the opportunity list, open each one's contacts and open activities in place, update next steps without leaving the review.
  • Account management: from one account row, see every open opportunity, case and contact, and edit across all of them.
  • Event and programme coordination: a parent record with participants, sessions and documents underneath it is exactly the shape this handles well.
  • Support triage: from a case list, see the account's other cases and recent activity before deciding what to do with this one.

‍

What it is not for

Related grids are an interface over your data, not a reporting layer. If the question is "how many across the whole org", that is a report. If the question is "what is going on with this record, and let me fix it", that is this.

‍

Permissions are the platform's own, unchanged. Users see and edit only the records they already have access to, and field-level security applies throughout.

‍

How to get started

  1. Install or upgrade via the AgentExchange listing or the Package Version page.
  2. Open a grid with related grids configured, and click the eye icon on any row.
  3. Use the sidebar to move between related grids, and hide it or the record row to suit how you work.

‍

Grids is free in sandboxes, with full features and no time limit, so you can build a related view over your own objects before deciding anything.

‍

Useful Links

‍

Thank You

Thanks to everyone who told us which related views they wanted and where the old one ran out of room. If there is a feature you need, tell us, because the roadmap is shaped by customers. Book a Call or Contact Us.

In this article:
Boost Salesforce Productivity with Grids & DocGen

40+ features to power up your workflows

Discover Grids
Discover DocGen
"A must have tool for efficient data management"

Alex Andony, Truly Investor Capital

AppExchange

Start working smarter in Salesforce