Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Navigating to records from Flows using LWC Local Actions

Reliable navigation from flows without flow errors. MSR-1202 | 2026-02

Within Mysolution, flows are used to navigate users from list views and record pages to specific records. Previously, two Aura components were available for this: navigateToRecord and safenavigateToRecord. Although these worked functionally, navigateToRecord caused flow errors in some scenarios due to cross-origin limitations.

With this feature, the existing Aura components have been replaced by a Lightning Web Component (LWC) Local Action, enabling future-proof, stable, and error-free navigation from flows.

 

Who is this feature relevant for?

This feature is relevant for:

  • Application administrators who configure flows with navigation actions

  • Users who start flows from list views or record pages

  • Organizations that use flows to create and immediately open records

 

Key benefits

  • No more flow errors when navigating to records

  • One uniform navigation component for multiple contexts

  • Future-proof solution based on LWC

  • Consistent user experience from both list views and record pages

 

 

Feature explanation

Transition to LWC Local Actions

Since Winter ’26, Salesforce supports LWC Local Actions in Screen Flows. These actions run directly in the browser and have access to navigation functionality without relying on Aura or Visualforce.

Based on this, a new LWC component has been developed that:

  • Can open records from a Flow

  • Does not cause cross-origin errors

  • Can be used from both list views and record pages

 

One component for all scenarios

Instead of two separate navigation components, a single central LWC component has been introduced. From both record page context and list view context, the navigation component is included in a Screen Flow, ensuring correct navigation within the overlay.

This prevents:

  • An empty flow overlay remaining visible

  • The page being unintentionally reloaded

  • Navigation occurring in an incorrect tab

 

Resolved issues

With this approach, the following issues have been resolved:

  • Cross-origin evaluation errors during navigation

  • Unreliable behavior of Aura components

  • Limitations when navigating from list views

 

Set-up / Implementation Time

To use this feature, the following is required:

  • Use of the new LWC Local Action in Screen Flows

  • For flows started from list views: include the navigation component in a Screen

  • Important: disable the Header and Footer of the screen component, otherwise navigation will not work!

Existing flows can be updated to use this new component. No data migration is required.

 

Other features in the 2026-02 release 

🔗 Please find an overview of other features in this release here.