Mobile metadata cache for capturing Medical Insights
Key Takeaway
For Medical Insights to be captured on mobile and sync back to the Salesforce org, an admin creates active Data-type object metadata cache configurations for the Medical Insights objects, assigns them to the profiles that use Medical Insights, and then generates a new metadata cache. A cache doesn't include an object that lacks an active configuration.
The Life Sciences Cloud Mobile app doesn't load every Salesforce object on its own. Before reps can capture Medical Insights on mobile, an admin must tell the app which Medical Insights objects to store locally and which records to download. The admin does so in two steps. First, create a configuration for each supported Medical Insights object. Then generate a metadata cache, which brings those settings to the app.
Configurations and the metadata cache
Configuration changes reach the app when you generate a metadata cache, so every Medical Insights mobile setup ends with generating one.
Selecting "Is Active" on a configuration is optional, but an inactive configuration is left out of the metadata cache. Generating a cache on its own doesn't include an object that lacks an active configuration. For example, if the DbSchema_MedicalInsight configuration exists but is inactive, the object it covers isn't in the cache. Leaving a configuration inactive is useful when you test a cache build without that object.
Creating configurations and generating the cache both require the "Life Sciences Commercial Admin" permission set. Both tasks start in the "Admin Console" of the Life Sciences Commercial app.