Loading

Life Sciences Cloud: Object Metadata Cache generation fails with 'DBSchema records are not found' or 'Default MobileAppName is not configured' error

Publish Date: May 26, 2026
Description

This article explains why Object Metadata Cache generation fails for the Life Sciences Cloud Mobile app and how to resolve it. Customers describe the issue as "while generating Metadata Cache the system is throwing the error: Errors occurred during validation: Metadata cache will not be generated if DBSchema records are not found" and "when generating Mobile cache for LSC mobile app, I get the error {"message":"Default MobileAppName is not configured in the org."}". Some users also see downstream errors when launching the iPad app such as "Applying the latest config failed", "Configuration Error: Failed to load app configuration", or "DBSchema: DeviceSyncTransactionRecord DB Schema configuration is missing or inactive". The error occurs in Admin Console > Mobile > Object Metadata Cache Configuration during the Validate or Create New Cache step. 

Resolution
Complete the steps below in order. Ensure the User has been assigned the Life Sciences Commercial Admin permission set.

Cause 1: DBSchema (Object Metadata Cache Configuration) records are missing
  1. From the App Launcher, find and open the Life Sciences Commercial app, then click Admin Console.
  2. Select Mobile > Object Metadata Cache Configuration. If the list is empty or only contains a few entries, the required DBSchema records are missing.
  3. Deploy the Salesforce Labs LSStarterConfig repository (lifeSciConfigRecord folder) into your org instead of creating them by hand. The deployment populates LifeSciConfigCategory [LifeSciConfigCategory] and LifeSciConfigRecord [LifeSciConfigRecord] metadata for all required objects.
  4. After deployment, return to Admin Console > Mobile > Object Metadata Cache Configuration and confirm records exist for the core required objects: User, Territory2, UserTerritory2Association, LifeSciMetadataRecord [LifeSciMetadataRecord], LifeSciMetadataCategory [LifeSciMetadataCategory], LifeSciMetadataFieldValue [LifeSciMetadataFieldValue], and DeviceSyncTransactionRecord [DeviceSyncTransactionRecord]. Add records for any feature-specific objects you use (Account, Visit, Presentation, AppAlert, Survey, ProductItem, MedicalInsight, and so on).


Cause 2: DBSchema records exist but are inactive or unassigned to the user's profile
  1. In Admin Console > Mobile > Object Metadata Cache Configuration, open each required record.
  2. Select the Is Active checkbox. Records that are not active are excluded from the cache.
  3. Set Type to Data for transactional objects (Account, Visit, MedicalInsight) and Configuration for setup objects (LifeSciMetadataRecord, LifeSciMetadataCategory, LifeSciMetadataFieldValue,).
  4. In the Assignment section, add the end-user profile that will use the mobile app (for example, Life Sciences Field Sales Representative or MSL profile). Do not generate the cache only against the System Administrator profile — generate it for the profiles assigned to the actual mobile users.
  5. Confirm DeviceSyncTransactionRecord [DeviceSyncTransactionRecord] is Active and assigned to every mobile user profile. A missing or unassigned DeviceSyncTransactionRecord produces the error "DBSchema: DeviceSyncTransactionRecord DB Schema configuration is missing or inactive".
  6. Verify the user profile has at least Read object-level access to every assigned object (for example, Activity Plan), otherwise the profile cannot be selected on the configuration record.


Cause 3: "Default MobileAppName is not configured in the org" error
1. Navigate to the Admin Console from the App Launcher.
2. Click on the Mobile tile.
3. In the left-hand navigation pane, select Application Settings (visible in the Mobile settings menu, usually below Profile Based App Settings).
4. Locate the field for Mobile App Name (or Default Mobile App Name).
5. Enter the appropriate name (e.g., Life Sciences Cloud or your custom app name).
6. Save the configuration.
7. Return to the Metadata Cache section and attempt to initiate/create the cache again.
Knowledge Article Number

005385078

 
Loading
Salesforce Help | Article