Deployment of Life Sciences Mobile Metadata Cache Configuration

Method 1: Manual Configuration (Salesforce Help Approach)

Reference:

• Salesforce Help: Create Object Metadata Cache Configuration

This method involves manually creating metadata configuration records through the application/admin console.

Limitation of Manual Approach

For enterprise customers with:

• Multiple profiles
• Large object models
• Many territories
• Large data volumes

manual creation becomes time-consuming and error-prone.

This is why Salesforce also provides a metadata deployment approach using metadata deployment tools.

Method 2: Bulk Deployment Using LSStarterConfig (Recommended)

Reference:

• GitHub Repository:
  SalesforceLabs/LSStarterConfig

This method deploys metadata configuration records in bulk using metadata deployment tools.

Supported Deployment Methods

The GitHub repository supports multiple deployment approaches:

Option A: VS Code / SFDX / Cursor

Steps

1. Clone or download the repository
2. Authenticate to org
3. Run: npm install
4. Execute deployment script:./data_load
5. Verify metadata records are created

Option B: Workbench Deployment

Important Packaging Requirement

When creating deployment ZIP files:

• package.xml must exist at the root level of the ZIP

Incorrect ZIP structure causes deployment failures.

Deployment Sequence

Deploy in this exact order:

1. inactive.zip
2. activate.zip

This sequence ensures metadata is created before activation occurs.

Important Recommendation: Configure Data Filters

Large-scale mobile sync without filters can cause:

• Timeout failures
• Excessive sync duration
• Large payload downloads
• iPad performance degradation

Always configure filters or SOQL-based restrictions so users only sync:

• Territory-specific accounts
• Assigned products
• Relevant records

Example use cases:

• Territory-based account filtering
• Country-based filtering
• Active account filtering

Generate Metadata Cache

After deployment:

1. Open Admin Console
2. Navigate to:
   Mobile → Metadata Cache Generation
3. Trigger generation process

Metadata Cache Lifecycle

Typical statuses:

What the System Validates

During generation, the platform validates:

• Managed package installation
• User licenses
• Translation Workbench configuration
• Near Core service connectivity
• Metadata configuration integrity

Mobile Application Initial Sync

After metadata becomes Active:

1. Install app using:
   • TestFlight (Sandbox)
   • App Store (Production)
2. Log into mobile application
3. Initial sync downloads:
   • Metadata cache
   • Layouts
   • Visibility rules
   • Filtered business data

Do not use simulators for validation testing.

Use physical iPad devices.

Validation Steps

After deployment and sync, validate the following:

Metadata Cache Validation

Confirm:

• Metadata cache status = Active
• No failed child processing records
• Near Core processing completed successfully

Mobile Validation

Validate users can:

• Log into iPad app
• Complete initial sync
• View assigned accounts
• Access layouts
• Create/update records

Sync Validation

Navigate to:

• Device Sync Transactions

Check for:

• Failed syncs
• Missing FLS
• Sharing issues
• Timeout errors

Failed syncs can often be retriggered by setting status back to:

Preparing

Common Issues and Troubleshooting

Recommended Best Practices

• Always validate in Sandbox first
• Use bulk deployment for enterprise implementations
• Enable Translation Workbench before cache generation
• Configure sync filters early
• Enable sharing triggers before data loading
• Validate using physical iPad devices
• Monitor Device Sync Transactions regularly
• Deploy inactive.zip before activate.zip