Custom Lightning page on mobile app: Lookup field not loading records

CRM Salesforce
, , , , , , , ,
1

Our field sales team uses the Salesforce mobile app extensively. We created a custom Lightning page for quick opportunity updates that includes a lookup field to link related accounts. The page works perfectly in desktop browser, but on the mobile app the lookup field shows no results when users search.

The component metadata includes:


<targets>
    <target>lightning__AppPage</target>
    <target>lightning__RecordPage</target>
</targets>

Field-level security is set to visible for the Sales profile. Field reps can’t link opportunities to accounts from mobile, which is blocking their workflow. Has anyone encountered lookup fields behaving differently on mobile versus desktop?

2

I’ve debugged similar mobile lookup issues before. The problem is usually not the lookup field itself but the search filter criteria. Mobile apps use a different search index than desktop, and if your Account records aren’t indexed properly for mobile search, they won’t appear in lookup results. Check Setup → Mobile Publisher → Salesforce Mobile App → Mobile Navigation and verify Account object is included. Also review any custom search layouts - mobile uses compact layouts differently than desktop.

3

Offline caching could definitely be a factor, but the main issue sounds like field-level security for mobile. Desktop and mobile apps handle FLS differently. Go to the Account object’s field accessibility settings and specifically verify that the Name field (which the lookup searches) is readable by the Sales profile. Also check if there are any record type restrictions or sharing rules that might filter out accounts on mobile. The mobile app applies stricter security contexts than desktop browsers in some cases.

4

After reviewing mobile lookup field issues extensively, here’s the complete solution:

1. Lightning Page Mobile Enablement Your metadata targets are incomplete. Update your component bundle to include mobile-specific targets:

<targets>
    <target>lightning__AppPage</target>
    <target>lightning__RecordPage</target>
    <target>lightningCommunity__Page</target>
    <target>lightningCommunity__Default</target>
</targets>

More critically, in the Lightning App Builder, ensure the page assignment includes the Salesforce Mobile App under “Form Factor” - this is separate from just activating the page.

2. Field-Level Security for Mobile Mobile apps enforce stricter FLS. Verify these settings:

  • Navigate to Account object → Fields → Name field
  • Check Field-Level Security for Sales profile: must be “Visible” AND “Read”
  • Go to the lookup field on Opportunity object and verify it’s also “Visible” for Sales profile
  • Critical: Check the Account object’s “Available for Mobile” setting under Mobile Administration

3. Component Metadata Mobile Targets If using any custom components within the Lightning page, each component needs mobile targets. Standard components should work, but verify your Lightning page doesn’t use any custom components that lack mobile support.

Testing Steps:

  1. Log into Salesforce mobile app as a Sales profile user
  2. Navigate to Setup → Mobile Publisher → Salesforce Mobile App
  3. Verify Account is in the Mobile Navigation menu
  4. Check that the Lightning page appears under the correct mobile context
  5. Test the lookup field - it should now show Account search results

Common Gotcha: The mobile app caches metadata aggressively. After making changes, users need to:

  1. Log out of the mobile app completely
  2. Clear the app cache (iOS: Settings → Salesforce → Clear Cache; Android: App Settings → Storage → Clear Cache)
  3. Log back in

The root cause is usually the missing mobile form factor assignment in Lightning App Builder combined with the mobile app’s metadata cache. Desktop browsers don’t cache as aggressively, which is why the page works there. Once you’ve added the proper mobile targets and cleared the cache, lookup fields should populate correctly on mobile devices.

5

It’s a standard Lightning lookup field, not a custom component. The entire Lightning page is activated for mobile in the App Builder. Could this be related to offline caching? Our reps sometimes work in areas with poor connectivity.

6

The issue is your component metadata targets. You’re missing the mobile-specific target. Lightning pages need explicit mobile enablement. Add this to your targets section: lightning__HomePage and more importantly, you need to check if your custom component is mobile-enabled. Standard lookup fields should work, but if you’re using a custom lookup component, it needs the mobile target defined.

7

Check if the lookup field’s related object (Account) has mobile-specific visibility settings. Sometimes object permissions work fine on desktop but mobile needs additional configuration in the Salesforce app settings.