Button on a Related List that Opens a Screen Flow

Key Takeaways

• Screen flow can replace related list New button
• Hack preserves native button look and feel
• No custom code required for automation
• Improves UX by keeping button location consistent
• Works for any object with related list

Summary

Salesforce admins often replace the standard New button on a related‑list with a custom solution to reduce fields and add automation. Common workarounds include building a Lightning Web Component or creating a parent‑record action, both of which alter the user experience. A screen‑flow “hack” lets you embed a button directly on the related list that opens a flow in a modal, preserving the native look while enabling complex logic. The author now uses this method for virtually every new‑record scenario.

Pulse Analysis

Salesforce administrators frequently wrestle with the limitations of the standard New button on related lists. The out‑of‑the‑box experience opens a full‑screen record page, which can overwhelm users with unnecessary fields and offers little room for pre‑populating data or triggering downstream processes. Traditional workarounds—such as developing a Lightning Web Component to override the button or adding a parent‑record quick action—solve the data‑entry problem but introduce a fragmented user interface. Users must learn two separate entry points, and the custom code adds maintenance overhead.

The screen‑flow hack sidesteps these issues by placing a custom button directly on the related list that launches a flow inside a modal dialog. Because the modal mimics Salesforce’s native button styling, users perceive it as the default New action, preserving familiarity while granting admins the flexibility to hide fields, set default values, and invoke complex automation without writing Apex or JavaScript. The flow can be built entirely in the Flow Builder, leveraging record‑create elements, decision logic, and input screens, making the solution accessible to declarative admins. This approach also respects Salesforce’s security model, inheriting the parent object’s sharing rules automatically.

From a business perspective, the hack reduces onboarding time for new users, cuts the number of clicks required to create a record, and eliminates the need for ongoing custom‑code maintenance. Organizations can roll out consistent data‑capture standards across multiple objects, ensuring higher data quality and faster pipeline velocity. For admins, the declarative nature of the solution accelerates delivery cycles and frees resources for higher‑value initiatives, while end‑users benefit from a seamless, native‑looking experience that aligns with their daily workflows.