Hi! Let’s troubleshoot why your Salesforce page prints missing tables — usually it’s the Printable View setup, page layout vs Lightning record page, or permissions that hide sections/related list tables when you print or “Save as PDF.”
To pinpoint whether this is Classic vs Lightning Experience behavior (or a browser issue), tell me:
• Are you printing a record detail page (Account/Case/Opportunity/custom object) or a list view?
• In Lightning, are you clicking Printable View, using the browser print dialog (Ctrl/Cmd+P), or exporting to PDF?
• What exactly is missing: related list tables (e.g., Contacts, Opportunities), fields/sections, or a “View All” table that appears on screen but disappears on paper?
• Does the same record print correctly in Salesforce Classic but not in Lightning?
• Any recent changes to page layout, Lightning App Builder (Lightning Record Page), Dynamic Forms, or Field-Level Security (FLS)?
Once I have those answers, I’ll walk you through the exact checks that restore the missing tables—without guessing and without breaking your layout.
Customer
We’re on Salesforce Lightning Experience. When users print an Opportunity record, the printed page is missing the related list tables (Products and Contact Roles) and sometimes even a section of fields. On screen it’s fine. If we switch to Salesforce Classic and print, the tables show up much more often. In Lightning we tried the Printable View action and also Ctrl+P in Chrome. Both ways we get a printout where the page looks “cut down” and the tables are just not there.
Got it — this is a common “Lightning prints missing tables” scenario. The key idea: the page you see on-screen in Lightning is a Lightning Record Page (components, tabs, “View All,” lazy-loaded related lists). But printing in Salesforce is usually based on Printable View rules, which depend heavily on the user’s page layout and related list settings — not necessarily the Lightning component view you’re looking at.
Here are the most frequent causes when Classic prints fine but Lightning doesn’t:
• The Printable View action isn’t properly available/added for that object’s Lightning actions, so users end up printing the interactive Lightning UI (which often hides tables).
• The missing “tables” are actually related lists that are collapsed, not on the user’s page layout, not in the correct related list set, or affected by user-specific related list preferences.
• Field-Level Security or object permissions cause Lightning to omit related list rows/columns in Printable View, even if Classic appears more forgiving.
• Browser printing (Chrome/Edge) can cut off Lightning components, especially when tables load after scrolling, when there are sticky headers, or when the print preview captures before the related list “View All” table is fully rendered.
We’ll fix it by forcing a reliable path: use Printable View for record printing, ensure the page layout includes the needed related lists, and confirm the user has the right FLS/permissions so the tables can actually render in printable output.
Customer
The Printable View action exists for some users but not all. Also, we recently changed the Lightning record page in App Builder and added a bunch of components and tabs. We’re also using Dynamic Forms on some objects. Could that make Printable View not match what’s on screen? And why would related list tables like Products or Contact Roles be missing only in print/PDF?
Yes — that explains the mismatch perfectly. Think of it like this: Lightning App Builder controls what users see in the browser, but Printable View is driven by page layout + actions + permissions. So it’s totally possible to have a beautiful Lightning record page and still have a Printable View that prints missing tables or missing sections.
Let’s do a reliable, step-by-step fix (this also helps maximize consistency for “Print to PDF”):
Step 1 — Make sure “Printable View” is available in Lightning for the object
1) Go to the object’s Page Layout used by the affected profile(s).
2) Find Salesforce Mobile and Lightning Experience Actions (or the Lightning actions section).
3) Confirm Printable View is present. If it’s missing for some profiles, they may be on a different page layout assignment.
Step 2 — Confirm the related list tables are actually on the Page Layout
On that same page layout, scroll to Related Lists and verify the lists you expect to print are included (e.g., Products, Contact Roles, Activities, custom related lists). Printable View usually reflects what’s on the page layout and the user’s related list preferences — not what’s merely visible via Lightning components/tabs.
Step 3 — Validate permissions that affect “missing tables”
If the related list is present but prints blank/missing, we check:
• Object permission for the related object (Read).
• Field-Level Security for the key lookup fields that tie the related list to the parent record.
• Any permission-set differences between the users who can print tables and the users who can’t.
After these three checks, Printable View usually stops “dropping” tables.
Customer
We checked: some users are on a different page layout assignment, and that layout didn’t have Products or Contact Roles in Related Lists. We added them. Now Printable View shows more, but one issue remains: in Lightning, the printed page still sometimes misses the related list rows (it shows the section header but not the table contents). It’s worse when users try Ctrl+P from the Lightning record page rather than using Printable View.
That’s the big difference: printing the Lightning UI (Ctrl/Cmd+P on the record page) is not the same as printing the Salesforce Printable View. Lightning pages are component-based and often load related list data asynchronously. A print preview can “snapshot” the page before the table rows fully render, especially if the user never clicked View All or never expanded a collapsed section/tab.
Here’s how to make the output consistent and stop “header shows but rows are missing” issues:
Step 4 — Standardize the workflow: always use Printable View for record printing
• On the record, click Printable View (not Ctrl+P on the Lightning record page).
• In the Printable View window/tab, make sure all relevant sections are expanded (some print views respect collapsed/expanded state).
• Then use the browser print dialog from that Printable View page.
Step 5 — If users must print from Lightning UI, force the tables to load first
• Open the related list “View All” table (or scroll until related lists fully load).
• Wait a few seconds for rows to render, then open Print Preview.
• Try Edge and Chrome (sometimes one handles long tables/page breaks better).
In short: Ctrl+P in Lightning is the least reliable method. Printable View is designed for printing and is the path that most closely matches Classic’s print behavior.
Customer
That helps. Another weird detail: Classic printing includes some fields that Lightning Printable View doesn’t show, even though the user can see them on the record page. We’re using Dynamic Forms for the “Details” section on Opportunity. Could that impact what Printable View pulls in? We also noticed a user with full access still gets missing fields in Printable View.
Yes — Dynamic Forms is a common reason the record page looks right but Printable View is missing fields. Dynamic Forms controls field visibility on the Lightning record page via component rules, but Printable View still leans on the Page Layout definition for what’s printable in many org setups. So Classic vs Lightning differences can show up even when users have access.
Here’s a clean way to diagnose “missing fields/tables” without chasing shadows:
Step 6 — Confirm what Printable View is actually using
1) Check the user’s Page Layout assignment for the object (not just the Lightning record page assignment).
2) On that page layout, ensure the missing fields are in the relevant sections.
3) For any field that still doesn’t print, verify Field-Level Security is set to Visible for that profile/permission set.
Step 7 — Related list “columns” can be permission-dependent
Even if a related list header appears, the table can render with missing columns or missing rows if the user lacks Read access to a key field used by the related list (for example, the lookup relationship field on the child object). In Lightning, related list rendering can be stricter about these permissions than Classic in certain edge cases.
If you tell me which related list is most affected (Products, Contact Roles, custom related list), I can point you to the exact permission check that typically makes the table appear reliably.
Customer
The biggest problem is Opportunity Products. Some users can see the products on screen but when printing, the table is empty or missing. They definitely have access to Opportunity. We also have a custom object related list that disappears in Lightning Printable View for one profile but prints in Classic.
Perfect — those two cases map to the most common Lightning printing “missing tables” root causes:
A) Opportunity Products table prints empty
Opportunity Products relies on underlying objects/permissions (like pricebook/product access in many orgs). If the user can see some UI parts but Printable View prints an empty table, we check:
• The page layout includes the Products related list (you already fixed layout assignment — good).
• The user has Read access to the related objects needed to render product rows (in many setups, this includes product/pricebook-related objects and fields).
• Any fields shown as columns in the related list have FLS Visible for that user (a missing key column can cause the printable table to render oddly or drop rows depending on configuration).
B) Custom related list disappears in Lightning Printable View for one profile
This often happens when Lightning enforces relationship-field access more strictly. Quick verification steps:
1) On the child object (the custom object in the related list), confirm the profile has Read access.
2) Confirm FLS Read/Visible on the lookup/master-detail field that relates it to the parent record.
3) Confirm the related list isn’t removed by a different Lightning page assignment or user-specific settings.
Once those are aligned, Printable View usually starts rendering the missing related list table rows in Lightning the same way you expect.
Customer
We fixed the custom related list by giving Read access to the lookup field on the child object for that profile. Now it prints in Lightning too. For Opportunity Products, using Printable View helps a lot. But some users still say the printed output cuts off after the first page and the rest of the table rows don’t print. This happens when the table is long.
Long tables are where browsers and web-app print views can get flaky — especially if users are printing the Lightning UI or if the table has sticky headers/scroll containers. Printable View is still the best route, but we can make it more reliable for big related list tables (lots of Opportunity Products rows).
Step 8 — Best practices for printing long Salesforce tables (PDF/Printer)
• Use Printable View first, then print from the browser print dialog on that page.
• Try Microsoft Edge if Chrome is truncating page 2+ (Edge sometimes handles long tables and page breaks more cleanly).
• In the print dialog, ensure you’re not printing “Selection only,” and consider turning off headers/footers if they push content off the page.
• If users are still missing rows, open the Printable View and use “Save as PDF” from that view rather than from the interactive Lightning page.
If you consistently need multi-page “tear sheets” with full related lists, a common strategy is to rely on Printable View for details and use a report/list view export for very long tables. But for most orgs, the changes you’ve made (layout + FLS + Printable View workflow) solve 90% of “prints missing table rows” complaints.
Customer
That explains it. So the main rule is: don’t print the Lightning record page directly; use Printable View, check page layout assignment, and validate FLS/permissions for related lists. Can you give us a quick checklist we can hand to admins when users complain that Salesforce prints missing tables in Classic vs Lightning?
Absolutely — here’s a tight admin checklist for the “
Salesforce page prints missing tables” issue (Classic vs Lightning):
Admin checklist (Printable View + missing related list tables)
1) Confirm the user is using
Printable View (not Ctrl/Cmd+P on the Lightning UI).
2) Verify the user’s
Page Layout assignment for the object, and confirm the needed
Related Lists are on that layout (Products, Contact Roles, custom related lists).
3) Check
Salesforce Mobile and Lightning Experience Actions includes
Printable View for that layout (users on a different layout often “lose” the action).
4) Validate
Object permissions (Read) for the related objects plus
Field-Level Security for key fields (especially relationship lookup fields on child objects).
5) If tables show headers but no rows, confirm related list columns rely on fields the user can read; remove/adjust columns if needed (permission-sensitive fields can break the render).
6) For long tables: print from Printable View and test Edge vs Chrome for page-break handling.
If you want, you can
open a chat and I’ll tell you exactly which permission or layout setting is causing the missing table in your specific object (Opportunity Products is a frequent one).
Customer
Perfect. After fixing page layout assignments, adding related lists, and correcting field permissions, Printable View now prints the tables reliably in Lightning. Classic vs Lightning finally makes sense. Thanks!
You’re welcome! Quick recap: when a
Salesforce page prints missing tables, the fix is usually to (1) print via
Printable View (especially in Lightning), (2) confirm the correct
page layout assignment includes the needed
related list tables, and (3) verify
object permissions + Field-Level Security so Lightning can render the rows/columns. Classic can look “more forgiving,” but Lightning Printable View is stricter about what the user can actually access.
If you hit another case where the Printable View is still missing related list rows, tell me the object + related list name and I can troubleshoot it with you step by step.
Start a chat and we’ll fix it fast.
Why Salesforce Lightning prints missing tables (but Classic may print them)
In Salesforce Classic, printing often follows a simpler detail-page flow. In Lightning Experience, the record page is component-based (tabs, dynamic visibility, lazy-loaded related lists). When users print the interactive Lightning UI, the browser may capture the page before related list tables fully render, resulting in missing related list rows or entire table sections.
The most consistent approach is to use the Salesforce Printable View action, which typically mirrors what’s available via page layout and the user’s related list preferences. If a table is missing in Printable View, it’s usually due to layout assignment, missing related lists, or permissions/FLS preventing the related data from being displayed. This is especially noticeable for custom related lists and lookup relationships where Lightning requires read access to key fields for the table to appear.
How to confirm it’s a Printable View/layout issue (not a browser glitch)
To isolate why a Salesforce record prints missing tables, compare outputs using the same record and user. First, click Printable View and print from that page. If the tables appear in Printable View but disappear when printing the Lightning UI, the issue is the browser printing the Lightning record page (timing, scroll containers, or page breaks). If the table is missing in Printable View itself, focus on page layout assignment, the Related Lists section, and FLS/object permissions.
For stubborn cases, test with another browser (Edge vs Chrome) and confirm the user isn’t on a different layout or Lightning page assignment. When a related list header shows but rows are empty, it’s frequently a field permission issue on the child object (especially the relationship field) or related list columns referencing fields the user can’t read.
Salesforce printing tips: missing related list tables in Classic vs Lightning
Use Printable View, validate page layout assignments, and confirm FLS to stop missing tables in print/PDF.
Fast path: ensure Printable View is available for the object in Lightning actions, verify the user’s page layout assignment includes the needed related list tables, and check Field-Level Security for key fields (especially lookup/master-detail relationship fields). For long tables like Opportunity Products, print from Printable View and try Edge if Chrome truncates page 2+.
Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your Salesforce org configuration (profiles, permission sets, page layouts, and Lightning record pages), please consult a verified expert on Whizz-Tech before making changes.
Why does my Salesforce page print missing tables in Lightning but not in Classic?
In Lightning Experience, the record page is component-based and related lists may load dynamically. Printing the Lightning UI (Ctrl/Cmd+P) can miss tables or rows. Use Printable View for consistent output, and verify the user’s page layout assignment includes the related lists and fields needed for printing.
Why are related list tables empty in Printable View even though users can see them on screen?
Most often it’s a permissions/FLS issue or a layout mismatch. Confirm the user has Read access to the related object, and check Field-Level Security for key fields (especially lookup/master-detail relationship fields). Also confirm the related list is included on the user’s assigned page layout and the columns don’t reference fields the user can’t read.
How do I add Printable View in Lightning Experience for users who don’t see it?
Open the object’s Page Layout used by that user’s profile, then check Salesforce Mobile and Lightning Experience Actions and add Printable View if it’s missing. If only some users are missing it, they’re often assigned to a different page layout.
What’s the best way to print long tables like Opportunity Products without missing rows?
Print from Printable View (not the Lightning UI), expand any collapsed sections, and then print from the browser. If Chrome truncates page 2+, test Microsoft Edge. For very large tables, consider printing record details via Printable View and exporting long lists separately via report/list view when needed.