Salesforce Mobile
Jitendra's Blog
Complete Salesforce Mobile Guide 2026

Salesforce Mobile Offline

Master offline capabilities with Briefcase Builder, LWC Offline, Mobile App Plus, data priming, synchronization, and conflict resolution

In This Guide
13
In-Depth Sections
Product Feature
50K
Max Records per Object
In This Guide
10
FAQs Answered
Security
256-bit
AES Encryption

1 What is Salesforce Mobile Offline?

Key Terms You'll Encounter

Before diving in, here are essential terms used throughout this guide:

  • Priming (Data Priming) – The process of preloading/downloading Salesforce records to a mobile device while online, so they're available for offline use later.
  • Briefcase – A container or configuration that defines which records should be downloaded to the device for offline access. Admins create briefcases using Briefcase Builder.
  • Draft Records – Records created or modified offline that are stored locally and queued for synchronization when connectivity is restored.
  • Sync (Synchronization) – The bidirectional process of uploading local changes to Salesforce and downloading server updates to the device.
  • SmartStore – The encrypted SQLite database on the mobile device where offline records are securely stored using 256-bit AES encryption.
  • Wire Adapter – LWC mechanism that connects components to Salesforce data. Offline-enabled wire adapters work without network connectivity.
  • LWC Offline – Lightning Web Components built to function without an internet connection using offline-capable wire adapters.

According to the official Salesforce documentation, Mobile Offline is a feature that transforms how field workers, sales representatives, and service technicians interact with Salesforce data in areas with limited or no network connectivity.

Core Capabilities

With Salesforce's LWC offline capabilities, you can:

Pro Tip: LWC Offline is available as an optional, opt-in enhancement to existing Salesforce mobile apps including the Salesforce Mobile App and Field Service Mobile App. According to Salesforce's developer blog, the Consumer Goods app support is also now available.
Key Numbers to Remember
50,000 — Max records per object
5 — Active briefcases per org
10 — Top-level object rules per briefcase
20 — Total object rules per briefcase
6 — Levels of hierarchy depth
10 — Filters per object
32 KB — Max GraphQL query size
256-bit — AES encryption strength

How Offline Access Works

Data Priming
Briefcase downloads selected records to device
While connected to WiFi
Local Storage
Records cached in encrypted SQLite database
256-bit AES encrypted
Offline Work
Create, edit, delete as draft records
Changes queued locally
Auto Sync
Drafts sync when connectivity restored
Conflict resolution

2 Mobile App Plus vs Standard Salesforce Mobile App

Understanding the difference between the standard Salesforce Mobile App and Salesforce Mobile App Plus is crucial for planning your offline strategy.

Standard Mobile App

  • Included free with every Salesforce license
  • Basic offline caching of recently viewed records
  • Limited offline editing capabilities
  • Uses standard Salesforce Mobile branding
  • Theme customization via standard settings

Mobile App Plus (Add-on)

  • Full Mobile Offline with Briefcase Builder
  • Mobile App Management (MAM) security
  • Custom branding and white-labeling
  • Publish to Apple/Google app stores
  • LWC-only architecture for performance

Mobile App Plus Features

According to Salesforce's official announcement, Mobile App Plus includes three core capabilities:

Feature Description Use Case
Mobile Offline Access Salesforce data with poor or no network connectivity using Briefcase Builder for data configuration Field technicians, remote sales, warehouse workers
Mobile App Management (MAM) Enhanced security with native mobile application management for additional security requirements Financial services, healthcare, regulated industries
Custom Branding Add company branding to the Salesforce Mobile App and publish to Apple and Google Play stores Enterprise branding, customer-facing apps
Important: While offline access does include some low-code admin data configurability, Mobile App Plus is primarily a pro-code offering. Customers need to build Lightning Web Components in a statically analyzable manner for full offline functionality.

Mobile Publisher vs Mobile App Plus

A common source of confusion is the relationship between Mobile Publisher and Mobile App Plus. These are different products serving different purposes:

Mobile Publisher

  • Creates branded apps from Experience Cloud sites
  • Wraps Salesforce Experience as native mobile app
  • Custom branding, splash screens, icons
  • Publish to Apple App Store/Google Play
  • Push notifications, barcode scanning
  • Designed for external users/customers

Mobile App Plus

  • Enhances Salesforce Mobile App
  • Full offline access with Briefcase Builder
  • Mobile App Management (MAM) security
  • Custom branding and white-labeling
  • LWC Offline architecture
  • Designed for internal users/employees
Key Distinction: Mobile Publisher is for creating branded apps from Experience Cloud sites (customer portals, partner communities). Mobile App Plus is an add-on for the internal Salesforce Mobile App with offline capabilities. They are not the same product and were not renamed—they coexist for different use cases.
Feature Mobile Publisher Mobile App Plus
Primary Purpose Branded apps for Experience Cloud sites Enhanced Salesforce Mobile App
Target Users External (customers, partners) Internal (employees, field workers)
Offline Capabilities Limited (Experience Cloud caching) Full offline with Briefcase Builder
Data Source Experience Cloud sites Salesforce CRM data
App Store Publishing Yes Yes
MAM Security No Yes

Licensing Considerations

The basic Salesforce Mobile App is included with every Salesforce license. However, Mobile App Plus is a separate add-on product. Contact Salesforce sales for specific pricing as it varies based on your existing licensing and user count.

3 Briefcase Builder Deep Dive

Briefcase Builder is the administrative tool that lets you define which records should be downloaded to mobile devices for offline access. It's the foundation of Salesforce's offline data strategy.

Briefcase Builder Workflow

1 Create Briefcase Give briefcase a name and description 2 Select Data Specify records for offline viewing 3 Add Assignments Designate users and groups to receive offline data 4 Select Apps Select applications to associate with briefcase 5 Activate Briefcase or Save for Later Make briefcase available immediately or save for later

What is a Briefcase?

A briefcase is a collection of filter rules that determine which records are primed (downloaded) to a user's device. Think of it as a personalized subset of your Salesforce data that travels with each mobile user.

Creating a Briefcase

According to the Salesforce Help documentation, follow these steps:

  1. Navigate to Setup — Go to Setup → Mobile Apps → Salesforce → Offline → Briefcase Builder
  2. Create New Briefcase — Click "New Briefcase" and provide a descriptive name
  3. Add Objects — Select standard or custom objects to include in the briefcase
  4. Define Filter Rules — Create conditions to limit which records are downloaded
  5. Assign to Users — Associate the briefcase with specific users or permission sets

Filter Rules and User Context

One of the most powerful features is the ability to filter records by User ID using the $User context variable:

// Example filter: Records owned by current user
{
    "object": "Account",
    "filterLogic": "OwnerId = $User.Id",
    "recordLimit": 500
}

// Example: Accounts in user's territory
{
    "object": "Account",
    "filterLogic": "Territory2Id IN ($User.UserTerritory2Association)",
    "recordLimit": 1000
}

Related Record Priming

According to Salesforce release notes, you can prime related records automatically:

Parent Object Related Objects Priming Behavior
Account Contacts, Opportunities, Cases Automatically includes child records
Work Order Service Appointments, Work Order Line Items Follows Field Service data model hierarchy
Custom Objects Lookup/Master-Detail relationships Configurable via Briefcase Builder rules
Best Practice: Start with fewer objects and records in your briefcase. The Salesforce Trailhead module on Offline Briefcase recommends including only the data needed to perform job functions, which improves sync times and device performance.

4 LWC Offline Development

According to the Mobile and Offline Developer Guide, building offline-capable Lightning Web Components requires understanding three technical pillars:

1. Data Priming

  • Intelligently preload records before going offline
  • Managed through Briefcase Builder
  • Advanced data replication rules and filters
  • Stores in durable, encrypted, on-device cache
  • LWCs access data from local cache when disconnected

2. Offline Data Manipulation

  • Create, edit, delete records while disconnected
  • Changes recorded as "drafts" in organized queue
  • Enhanced UI API operations work with queue
  • No manual sync management required
  • Automatic change tracking

3. Automatic Synchronization

  • Queued changes sync when reconnected
  • Handles operation sequencing automatically
  • Built-in conflict resolution
  • Maintains data integrity across devices
  • Status feedback to users

Supported Wire Adapters

According to LWC documentation, these wire adapters work offline:

Wire Adapter Module Offline Support
getRecord lightning/uiRecordApi Full Support
getRecords lightning/uiRecordApi Full Support
graphql lightning/uiGraphQLApi Full Support
getRelatedListRecords lightning/uiRelatedListApi Partial*
getRelatedListCount lightning/uiRelatedListApi Partial*
*Important Limitation: According to Salesforce developer documentation, getRelatedListRecords and getRelatedListCount won't reflect records created or deleted while offline, despite providing offline support functionality.

GraphQL Wire Adapter for Offline

The GraphQL wire adapter is recommended for offline scenarios. According to Salesforce's official guidance, here's why:

Aspect getRecord / LDS Adapters GraphQL Wire Adapter
Server Requests Multiple round trips needed for complex data Single request aggregates data across resources
Relationships Requires chaining multiple wire adapters Traverse relationships in one query
Filtering & Sorting Limited filtering capabilities Complex filtering, sorting, pagination built-in
Data Efficiency May return extra fields Query exact fields needed—lightweight payloads
Bandwidth Usage Higher (redundant data) Minimal (critical for constrained networks)
Create/Update/Delete Full CUD support Read-only (use LDS for mutations)
Known Record IDs More efficient Works but LDS is simpler
When to Use Each:
  • Use GraphQL — Complex queries, traversing relationships, filtering/sorting lists, minimizing data transfer for offline priming
  • Use getRecord/LDS — Simple single-record retrieval with known IDs, creating/updating/deleting records

GraphQL Code Example

import { LightningElement, wire } from 'lwc';
import { gql, graphql } from 'lightning/uiGraphQLApi';

export default class OfflineAccountList extends LightningElement {
    @wire(graphql, {
        query: gql`
            query getAccounts {
                uiapi {
                    query {
                        Account(first: 10) {
                            edges {
                                node {
                                    Id
                                    Name { value }
                                    Phone { value }
                                }
                            }
                        }
                    }
                }
            }
        `
    })
    accounts;
}
Performance Warning: Large GraphQL queries (many or big fields exceeding 32 KB) can negatively affect mobile app performance. The Salesforce Mobile Extensions for VS Code flags large queries during development.

Real-World Scenario: When GraphQL Shines

Consider a field technician's mobile app that needs to display:

With LDS (Multiple Adapters)

  • getRecord for Service Appointment
  • getRecord for Work Order
  • getRecord for Account
  • getRelatedListRecords for Contacts
  • = 4+ server round trips
  • = 4+ wire adapters to manage

With GraphQL (Single Query)

  • One query traverses all relationships
  • Filter by date, sort by time
  • Request only needed fields
  • = 1 server request
  • = 1 wire adapter
  • = Less data primed offline

Development Tools

Salesforce provides specialized tools for offline LWC development:

5 Data Priming & Synchronization

Understanding how data flows between Salesforce servers and mobile devices is essential for building reliable offline applications. According to Salesforce documentation, this process involves priming and synchronization.

What is Data Priming?

Data priming is the process of downloading selected records from Salesforce to the mobile device's local storage before the user goes offline. The device periodically syncs while still online, ensuring users have access to records if connectivity is lost.

Sync Down Process

According to the Mobile SDK documentation:

Server Query
Execute briefcase filter rules on server
Apply user context
Download
Transfer matching records to device
Encrypted transfer
SmartStore
Store in local encrypted SQLite database
Indexed "soups"

Sync Up Process (Draft Records)

When users make changes offline, those changes are recorded as drafts. According to Salesforce's sync up documentation:

  1. Local Change Detection — System identifies created, updated, or deleted records in local storage
  2. Queue Management — Changes are organized in a queue with proper sequencing
  3. Server Replication — When online, changes are applied to Salesforce server
  4. Confirmation & Cleanup — Successful syncs clear draft flags; failures remain queued

Ghost Records

According to the Offline Management documentation, "ghost records" are local records that correspond to server records that have been deleted. The sync down payload doesn't reflect server-side deletions, so these records remain in local storage until explicitly cleaned up.

Developer Note: Call cleanResyncGhosts methods after sync down to remove ghost records from local storage. This maintains data consistency between the device and server.

6 Conflict Resolution

When multiple users can collaborate offline, conflicts are inevitable. According to Salesforce's conflict detection documentation, the platform provides built-in mechanisms to handle these scenarios.

Conflict Detection Architecture

The Mobile SDK supports conflict detection with any save operation, regardless of whether the device is returning from an offline state. To enable conflict detection, you specify a secondary cache containing the original values fetched from the server.

Three Data States

Conflict detection compares three versions of the same record:

BASE
Original record fetched from server
YOURS
Current local record (your changes)
THEIRS
Current server record (their changes)

Merge Modes

Merge Mode Behavior Use Case
OVERWRITE Blindly writes all local values to server without comparing Simple scenarios, single-user apps
MERGE_ACCEPT_YOURS Local changes win for modified fields; unchanged fields preserve server values Mobile-first workflows where field users have authority
MERGE_FAIL_IF_CONFLICT Fails if both client and server changed the same field Critical data requiring manual review
MERGE_FAIL_IF_CHANGED Fails if any field was changed on the server Maximum safety, no server changes allowed

Visual: How Merge Modes Work

Consider a scenario where Client changes fields A & B and Server changes fields B & C:

 Field Changes Comparison
Field
Base (Original)
Yours (Client)
Theirs (Server)
Field A
Value 1
Value 1-A
Value 1
Field B
Value 2
Value 2-B
Value 2-C
Field C
Value 3
Value 3
Value 3-C

Legend: Green = Changed | Red = Conflict (both changed)

Results by Merge Mode

OVERWRITE

  • A: Value 1-A (yours)
  • B: Value 2-B (yours)
  • C: Value 3 (yours)
SUCCESS - Server's C overwritten!

MERGE_ACCEPT_YOURS

  • A: Value 1-A (yours)
  • B: Value 2-B (yours wins)
  • C: Value 3-C (theirs kept)
SUCCESS - Smart merge!

MERGE_FAIL_IF_CONFLICT

  • Field B: Both changed!
  • Conflict detected
  • Manual resolution needed
FAILS - Conflict on B!

User Experience for Conflicts

According to Salesforce's offline editing documentation, users can view and manage conflicts from the Pending Changes page in the mobile app:

Multi-User Collaboration: According to Salesforce's Mobile App Plus announcement, multiple users can collaborate together offline with built-in data reconciliation and conflict resolution. Edits are automatically synced to the cloud when back online.

7 Security & Encryption

Offline data security is paramount, especially when sensitive customer information is stored on mobile devices. According to Salesforce's local data protection documentation, multiple layers of encryption protect offline data.

SmartStore Encryption

According to the SmartStore documentation, SmartStore is built on SQLite and uses SQLCipher to encrypt customer data:

Encryption Layer Technology Key Size
Database Encryption SQLCipher 256-bit AES
Key Storage (iOS) iOS Keychain 256-bit AES
Master Key Protection 256-bit ECC Equivalent to 3072-bit RSA
Encryption Mode AES-GCM (since SDK 9.2) 256-bit

SQLCipher Support

Starting in Mobile SDK 13.0, SmartStore supports:

iOS Key Storage Architecture

According to Salesforce's iOS security documentation:

Security Architecture: In iOS, each type of customer data uses its own unique key. These keys are stored in the iOS keychain and encrypted by a master key. The master key is accessible only to the app and is secured with an industry-standard 256-bit AES key, protected by a 256-bit elliptic curve cryptography (ECC) private key.

Mobile App Management (MAM)

For organizations with additional security requirements, Mobile App Plus includes MAM capabilities:

8 Governor Limits & Constraints

Understanding the limits and considerations for Salesforce Mobile Offline is crucial for successful implementations.

Briefcase Builder Limits

Limit Type Maximum Value Notes
Active Briefcases per Org 5 Total active briefcases allowed
Top-Level Object Rules per Briefcase 10 Primary objects in briefcase
Total Object Rules per Briefcase 20 Including top-level + related rules
Levels of Hierarchy (Related Objects) 6 Depth of related object rules
Records per Object 50,000 Default is 500 records per object
Total Records Across All Briefcases 50,000 Per org, across all active briefcases
Filters per Object 10 Use indexed fields for performance
Custom Metadata Type Rules 10 Per briefcase
GraphQL Query Size 32 KB Optimize field selection
Performance Recommendations: Salesforce recommends including as few objects and records as needed. Use indexed fields for filters (unindexed fields show orange warning). For Order By, select Sysmodstamp for optimal performance. Apply at least 1 filter per object.

Unsupported Objects

The following objects are not supported in Briefcase Builder:

Supported: Standard and custom objects that are customizable and layoutable. Person accounts are supported with fields available as filters on the Account object.

Field Service Mobile Specific Limits

According to Field Service Mobile App Limitations:

Limit Value Notes
Records per Related List 50 List indicator shows "(50+)" if more exist
Priming Hierarchy Depth 1,000 page references Priming fails if exceeded
Recommended Parent Records 100 e.g., Work Orders, Accounts
Child Records per Parent 10 e.g., Service Appointments per Work Order

LWC Offline Limitations

According to Salesforce's offline considerations, LWC Offline has these constraints:

Critical Gotcha: Server-side logic (Apex triggers, validation rules, workflow rules, flows) does NOT execute when records are created or modified offline. These only run when data syncs to the server. Design your offline experience accordingly!

9 Salesforce Mobile Apps Ecosystem

Salesforce offers multiple mobile apps tailored for different use cases and industries. Understanding which app fits your needs is essential for successful mobile offline implementations.

Official Salesforce Mobile Apps

App Primary Use Case Offline Support
Salesforce Mobile App General CRM access for Sales Cloud, Service Cloud, and custom apps Via Mobile App Plus add-on
Field Service Mobile Field technicians, on-site service workers, dispatchers Built-in offline-first design
Consumer Goods Cloud Retail execution, store visits, merchandising, inventory audits Built-in offline capabilities
Salesforce Maps Route optimization, territory management, location intelligence Offline map caching
Note: Sales Cloud and Service Cloud functionality is accessed through the main Salesforce Mobile App, not as separate standalone apps. Mobile App Plus enhances the Salesforce Mobile App with offline capabilities.

Salesforce Mobile App

The Salesforce Mobile App is the general-purpose mobile application for accessing Salesforce CRM on iOS and Android devices. It provides mobile access to Sales Cloud, Service Cloud, and custom Lightning applications.

Key Features

Mobile App Plus for Offline

According to Salesforce documentation, Mobile App Plus is an add-on license that enables offline capabilities for the standard Salesforce Mobile App. With Mobile App Plus:

Licensing Note: Mobile App Plus is a separately licensed add-on. The standard Salesforce Mobile App is included with most Salesforce editions but requires online connectivity.

Field Service Mobile App

The Field Service Mobile App is purpose-built for mobile workers who spend most of their time away from the office—technicians, installers, inspectors, and service professionals who need reliable access to job information regardless of connectivity.

Who It's For

Key Features

Offline Priming Approach

According to offline considerations documentation, Field Service Mobile uses a hierarchical priming approach:

  1. Service Resource Profile — System identifies the logged-in user's service resource record
  2. Assigned Work — Downloads Service Appointments assigned to the resource
  3. Parent Work Orders — Primes parent Work Order records for each appointment
  4. Related Records — Downloads Work Order Line Items, Assets, and configured custom objects

Consumer Goods Cloud Mobile App

The Consumer Goods Cloud Offline Mobile App enables field representatives to execute retail visits and record store data even in areas with poor or no internet connectivity.

Who It's For

Key Features

According to Trailhead documentation:

Licensing: The Consumer Goods Cloud Offline Mobile App is included with Consumer Goods Cloud subscription at no additional licensing fees.

Salesforce Maps

Salesforce Maps is a location intelligence platform that helps field sales teams optimize routes, manage territories, and visualize customer data geographically. While not a standalone offline app, it integrates with the Salesforce Mobile App to provide powerful location-based features.

Who It's For

Location Intelligence

Salesforce Maps transforms how teams visualize customer data by plotting accounts, opportunities, and any Salesforce object on interactive maps. According to Trailhead, users can filter and prioritize accounts based on:

Route Optimization

Route optimization is a core strength of Salesforce Maps, helping field teams reduce travel time and maximize customer-facing hours:

Territory Planning

Sales managers can visualize and manage territory assignments directly from the map interface:

Mobile Features

According to Salesforce Help, Salesforce Maps mobile capabilities include:

Pricing

Salesforce Maps is available in two tiers:

Adding Custom Objects via Briefcase

For Field Service Mobile and Mobile App Plus, custom objects from outside the standard data model hierarchy can be added to a briefcase so workers can access the data offline. This is particularly useful for:

10 Best Practices & Gotchas

Based on Salesforce Trailhead recommendations and official documentation, here are essential practices for successful offline implementations.

Do's - Best Practices

Briefcase Configuration

  • Start with minimum required objects and records
  • Use $User context for personalized data
  • Test with realistic data volumes
  • Monitor sync times and adjust limits

LWC Development

  • Use Salesforce Mobile Extensions for VS Code
  • Keep GraphQL queries under 32 KB
  • Test in airplane mode during development
  • Implement proper error handling for sync failures

User Experience

  • Show clear offline/online indicators
  • Provide pending changes visibility
  • Train users on manual sync procedures
  • Design for worst-case connectivity scenarios

Don'ts - Common Gotchas

Server-Side Logic Doesn't Run Offline: Apex triggers, validation rules, workflow rules, and flows only execute when data syncs to the server. Never rely on server-side logic for offline data validation or business rules.
Related List Counts Are Static: getRelatedListRecords and getRelatedListCount wire adapters won't reflect records created or deleted while offline. The counts update only after sync.
Priming Failures Are Silent: If priming fails due to exceeding 1,000 page references, users may not realize their data is incomplete. Always validate briefcase configurations thoroughly.
Gotcha Impact Mitigation
Large briefcases slow sync Poor user experience, battery drain Limit records, use targeted filters
Ghost records accumulate Stale data, storage issues Call cleanResyncGhosts regularly
Unsupported base components UI errors offline Test all components in airplane mode
Required fields missing Sync failures on server Client-side validation for required fields

11 Frequently Asked Questions

Salesforce Mobile Offline is a feature that allows mobile users to access, create, edit, and delete Salesforce records even without an internet connection. Data is stored locally on the device using encrypted storage (256-bit AES via SQLCipher) and automatically syncs when connectivity is restored. It's available through Mobile App Plus or Field Service Mobile.

Briefcase Builder is an admin tool that lets you define which records should be downloaded to mobile devices for offline access. You can create filter rules, set record limits per object (up to 100,000), use dynamic user context ($User variables), and configure related record priming. It's accessible via Setup → Mobile Apps → Salesforce → Offline → Briefcase Builder.

Briefcase Builder supports up to 100,000 records per object, though Salesforce recommends keeping it under 500 records per object for optimal performance. Related lists are limited to 50 records per list, and the priming hierarchy cannot exceed 1,000 page references. For Field Service, recommend 100 or fewer parent records with 10 or fewer child records each.

Salesforce Mobile Offline supports multiple merge modes: MERGE_ACCEPT_YOURS (client changes overwrite server for modified fields, unchanged fields preserve server values), and MERGE_FAIL_IF_CONFLICT (operation fails if both client and server changed the same field). Changes made offline are queued as drafts and synced automatically when online. Users can view and manage conflicts from the Pending Changes page.

Mobile App Plus is a paid add-on that includes three features: Mobile Offline access for working without connectivity, Mobile App Management (MAM) for enhanced security with native application management, and custom branding to publish to Apple/Google app stores. The standard Salesforce Mobile App is included free with every license but has limited offline capabilities (basic caching of recently viewed records).

Mobile Publisher creates branded mobile apps from Experience Cloud sites for external users (customers, partners). It wraps your community/portal as a native mobile app with custom branding.

Mobile App Plus enhances the Salesforce Mobile App with offline capabilities (Briefcase Builder), MAM security, and branding for internal employees.

They are separate products serving different purposes and were not renamed—they coexist in the Salesforce mobile ecosystem.

The following wire adapters are offline-enabled:

  • @salesforce/graphqlRecommended for offline (single query, multiple objects)
  • getRecord / getRecords — Get record data by ID
  • getRelatedListRecords — Fetch related list records
  • getRelatedListCount — Get count of related records
  • getPicklistValues / getPicklistValuesByRecordType — Picklist metadata
  • getObjectInfo / getObjectInfos — Object metadata

Not supported offline: getListUi, getRecordUi, Apex @wire methods, imperative Apex calls.

No. Apex code runs exclusively on Salesforce servers and cannot execute offline. This includes:

  • Apex triggers (insert, update, delete)
  • Validation rules
  • Workflow rules and Process Builder
  • Flows (except client-side screen flows)
  • @wire Apex methods and imperative Apex calls

All server-side logic executes only when the device syncs back online. Design your offline experience to handle client-side validation and expect server-side rules to run during sync.

When sync fails, records remain as drafts in the pending changes queue. Common failure reasons include:

  • Validation rule failures — Server-side rules reject the data
  • Required field missing — Fields required on server weren't populated
  • Trigger exceptions — Apex trigger throws an error
  • Conflict detection — Same field changed by another user (with MERGE_FAIL_IF_CONFLICT)

Users can view failed records in the Pending Changes screen, edit them to fix issues, and retry sync. Records can also be discarded if needed.

12 Abbreviations & Glossary

Abbreviations & Glossary

Reference guide for technical terms and abbreviations used throughout this article.

AES - Advanced Encryption Standard (256-bit encryption used by SmartStore)
API - Application Programming Interface
CGC - Consumer Goods Cloud (retail execution platform)
CRM - Customer Relationship Management
DML - Data Manipulation Language (create, update, delete operations)
ECC - Elliptic Curve Cryptography
FIPS - Federal Information Processing Standards (140-2 compliance)
FSM - Field Service Mobile (offline-first app for technicians)
GA - Generally Available (production-ready release)
GraphQL - Graph Query Language (recommended for offline LWC)
LDS - Lightning Data Service (wire adapters for data access)
LWC - Lightning Web Components
MAM - Mobile App Management (enterprise security feature)
MCF - Mobile Customization Framework
Mobile Publisher - Tool to create branded apps from Experience Cloud sites
POI - Point of Interest (Salesforce Maps search feature)
SDK - Software Development Kit (Mobile SDK for native apps)
SmartStore - Encrypted SQLite database for offline storage
SOQL - Salesforce Object Query Language
SQLCipher - Open-source SQLite encryption extension
UI API - User Interface API (powers LDS wire adapters)
VS Code - Visual Studio Code (IDE with Mobile Extensions)

Related Reading

Continue your Salesforce mobile and security learning journey with these related guides:

Link copied to clipboard!
Previous Post
Salesforce Spring ’26 Release: Complete Guide 2026
Archives by Year
2026 4 2025 16 2024 2 2023 9 2022 8 2021 4 2020 18 2019 16 2018 21 2017 34 2016 44 2015 54 2014 30 2013 31 2012 46 2011 114 2010 162
Search Blog

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Discover more from Jitendra Zaa

Subscribe now to keep reading and get access to the full archive.

Continue Reading