Generating the metadata cache after configuration changes
Key Takeaway
Configuration changes such as page layouts don't reach the Life Sciences Cloud mobile app until an admin generates a new metadata cache in the Admin Console and mobile users download it.
The metadata cache is a bundle of object schemas and metadata definitions that the Life Sciences Cloud mobile app stores on the device. Think of it as the app's local copy of your org's setup, which is how the app supports both online and offline modes. When admins change configuration, they sync the changes to the app by generating a new metadata cache. Mobile users then download the new cache.
When to generate a new metadata cache
The mobile app works from its local copy, so a change you save in the org doesn't reach the app on its own. The change shows in the mobile app only after an admin generates a new metadata cache and users download it. The app stays on its old copy even if you can already see the change in Salesforce on desktop.
Generate a new metadata cache whenever you update any of these, because these configuration changes are synced to the mobile app through the cache:
- Lightning record pages
- Page layouts
- Objects or schema
- Feature settings, new or modified
- Permissions
Saving a setting in the Admin Console isn't enough to change the mobile app either. For example, you set mobile sync settings at the org default or user profile level. Those settings reach the app only after you create a metadata cache.
Marco, an admin, changes the Lightning record page for accounts so that a new tab appears. He opens an account in Salesforce on his laptop and sees the new tab. Ana, a sales rep, opens the same account in the Life Sciences Cloud mobile app, and the tab isn't there because her app still uses the old metadata cache. Marco generates a new metadata cache in the Admin Console. After Ana downloads the new cache, the tab shows up in her app.