Dynamic Related Lists for Salesforce Mobile App (Beta) — Summer ’25 | Dynamic Related Lists Mobile

If you’ve been struggling with cluttered record pages on your phone, the Summer ’25 release finally introduces Dynamic Related Lists Mobile (Beta) to help clean things up. I’ve seen so many field reps get frustrated because they have to scroll through dozens of irrelevant records just to find one specific update. It’s a massive waste of time, and honestly, it’s one of those things that makes people stop using the app altogether.

Why You Need Dynamic Related Lists Mobile

The desktop version of this feature was a huge win for admins, so bringing it to the phone just makes sense. So what does this actually mean for your users? It means you can finally use descriptive filters to show only the records that matter in the moment. For example, instead of showing every single Case related to an Account, you can show a filtered list of just “Open High-Priority Cases” right at the top of the mobile screen.

This level of control is similar to what we’ve seen with Salesforce Dynamic Forms vs Record Types where the goal is to reduce noise. When your team is out in the field, they don’t have the patience to hunt for data. They need the right info, right now. By using Dynamic Related Lists Mobile, you’re basically giving them a shortcut to the data they actually use to do their jobs.

How to Enable Dynamic Related Lists Mobile

Here’s the thing: this isn’t turned on by default. You’ll need to head into Setup to flip the right switches. It’s a two-step process that catches some people off guard. You can’t just enable the related lists without first making sure your mobile org is ready for dynamic content in general.

  • Go to Setup and search for Salesforce mobile app.
  • First, make sure Dynamic Forms and Dynamic Highlights Panel on Mobile is toggled on.
  • Then, look for the Dynamic Related Lists for Mobile (Beta) toggle and enable it.

Once those are active, you can jump into the Lightning App Builder. When you’re configuring your record pages, you’ll see the option to use the Dynamic Related List – Single component for your mobile layouts. It’s a pretty straightforward setup once the org-wide settings are handled.

Design for the Thumb, Not the Mouse

One thing that trips people up is trying to copy their desktop layouts exactly. Don’t do that. A desktop screen can handle six or seven columns of data, but on a phone, that’s a nightmare to read. You’ll end up with a horizontal scrolling mess that nobody wants to deal with.

In my experience, mobile users only care about two or three key fields. If you are showing a list of Opportunities, just give them the Name, the Stage, and the Close Date. Anything else is just clutter that gets in the way of the “New” or “Edit” buttons.

Testing and Beta Risks

Since this is a Beta feature, you have to be a bit careful. I always tell people to check their Salesforce Sandbox Types and pick a good environment for testing before rolling this out to everyone. You don’t want to find out that a complex filter is breaking the mobile view while your CEO is trying to look up a record during a meeting.

Look, Beta means things can change. Salesforce might tweak how the filters work or how the UI renders in the next release. Keep an eye on the release notes and be ready to make small adjustments. It’s a small price to pay for getting these features early and making your mobile users’ lives a lot easier.

Key Takeaways

  • Dynamic Related Lists Mobile helps reduce scrolling by showing only relevant records to users on the go.
  • You must enable both Dynamic Forms for Mobile and the specific Beta toggle in Setup before you can use it.
  • Keep your mobile columns limited to 2-3 essential fields to maintain a clean user interface.
  • Always test your filters in a sandbox because Beta features can behave differently than production-ready tools.
  • This feature is a major step toward making the mobile app feel as powerful as the desktop experience.

At the end of the day, this update is about making the mobile experience less about “data entry” and more about “data consumption.” If you can save a rep thirty seconds of scrolling every time they open a record, that adds up fast over a week. Start small, pick one high-impact object like Opportunities or Cases, and see how your team likes the new view.