Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More

Salesforce Life Sciences Cloud: Actions and Lightning Web Components (LWC) behave differently in the LSC Mobile App and Lightning Experience

Publish Date: Jul 6, 2026
Description

This article applies to Salesforce Life Sciences Cloud (LSC) when actions, Lightning Web Components (LWC), FlexCards, or list view features behave differently between Lightning Experience and the LSC mobile app.

Customers may observe symptoms such as:

  • An embedded or Intelligent Content action is available in the mobile app but not in Lightning Experience.
  • An Attach PDF or other quick action appears in one client but not the other.
  • An LWC or FlexCard is not displayed on desktop or mobile.
  • Certain list view columns (such as Specialty or Last Visit) cannot be sorted in Lightning Experience.
  • Record page behavior differs between desktop and mobile.

These differences are typically caused by differences in Lightning Record Page assignments, page layouts, component visibility filters, supported platform capabilities, or mobile-specific page configurations.

Resolution

Determine which scenario matches the observed behavior.

Scenario 1: A quick action is available in one client but missing in another

  1. Navigate to Setup > Object Manager > [Object] > Page Layouts.
  2. Open the page layout assigned to the affected users.
  3. Verify that the required action is included in the Salesforce Mobile and Lightning Experience Actions section.
  4. If the action exists only under Salesforce Classic Publisher Actions, move it to Salesforce Mobile and Lightning Experience Actions.
  5. Save the layout.

If the action is provided through a Lightning Record Page:

  1. Open Setup > Lightning App Builder.
  2. Open the record page assigned to the object.
  3. Verify the component or action is configured for the required form factor.
  4. Review Component Visibility filters to ensure they do not exclude the affected users or devices.
  5. Save and activate the page.

Scenario 2: List view columns cannot be sorted

Not every list view column supports sorting.

Sorting is unavailable for columns based on:

  • Formula fields
  • Related-object fields
  • Certain calculated or derived values

If sorting is required, use a stored field on the base object instead of a calculated value and add that field to the list view.

Scenario 3: Different behavior between desktop and mobile

If functionality differs between clients:

  1. Verify the same Lightning Record Page is assigned to both desktop and mobile users.
  2. Confirm the same page layout is assigned for the user's profile and record type.
  3. Review any form-factor-specific component visibility settings.
  4. Verify the feature is supported on both Lightning Experience and the Salesforce mobile application, as some capabilities are platform-specific by design.

Additional Checks

  • Confirm the correct record page is activated for the affected App, Record Type, and Profile.
  • Review Dynamic Actions and Dynamic Forms configuration if they are in use.
  • Verify any custom LWCs, FlexCards, or custom actions do not contain client-specific logic.
  • Test using the latest version of the Salesforce/LSC mobile application.

After making configuration changes, reproduce the same scenario in both Lightning Experience and the LSC mobile app to verify that the action, component, or functionality behaves

Knowledge Article Number

005387744

 
Loading
Salesforce Help | Article