Loading
Scheduled maintenance for Salesforce HelpRead More
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Create Object Metadata Cache Configuration

            You are here:

            1. Salesforce Help
            2. Docs
            3. Agentforce Life Sciences

            Create Object Metadata Cache Configuration

            The Life Sciences Cloud Mobile app doesn’t automatically load all Salesforce objects and related data. Configure the object metadata cache to define which objects the mobile app stores locally and whether data syncs one-way or two-way between your Salesforce org and the mobile app. This configuration makes sure your sales reps have access to the data they need in the mobile app.

            Required Editions

            Available in: Lightning Experience
            Available in: Enterprise and Unlimited Editions with Life Sciences Cloud, Life Sciences Cloud for Customer Engagement Add-on license, and the Life Sciences Customer Engagement managed package.
            User Permissions Needed
            To create metadata cache configuration: Life Sciences Commercial Admin permission set

            The LifeSciConfigCategory and LifeSciConfigRecords metadata types must have records populated in order to generate metadata.

            1. From the App Launcher, find and select the Life Sciences Commercial app.
            2. Click Admin Console.
            3. Select Mobile and then select Object Metadata Cache Configuration.
            4. Click New and enter the configuration details.
              1. Enter a unique name that describes the object.
              2. To make the object available for inclusion in the metadata cache, select Is Active.
                Note
                Note Selecting Is Active is optional. However, if you don’t select it, the object isn’t included in the metadata cache. For example, in some cases, you may leave the configuration inactive when setting up the object for the first time or when testing a cache build without the object in it.
              3. Select the object type to determine how the object data is used in the mobile app.
                • Data: The object contains business or transactional data that sales reps directly interact with in the mobile app.
                • Configuration: The object contains configuration data that controls the mobile app’s behavior and isn’t visible to sales reps.
                • Data Model Object: The object contains a data model object stored in the Data Cloud.
              4. Select an object or a configuration record based on the type you selected.
                • If you select data or configuration as the type, search for and select a value in the Object field.
                • If you select a data model object as the type, enter details in the Data Space API Name and Data Model Object API Name fields.
              5. For Assignment, select one or more profiles to which this configuration applies.
                Note
                Note The Assignment field appears only after you select an object. Profiles with at least Read access to the object can see the assignment list.
              6. In Delta Sync Data Field, enter the field name used to determine incremental sync for the selected object.
                Records with a field value greater than the last recorded sync value are included in the next sync cycle. This field is only applicable when you select data as the type.
              7. To sync data only from Salesforce to the mobile app, select Allow only one-way sync from web to mobile.
              8. Select the Attachment Download Method.

                An internet connection is required for download. This field supports:

                • Background: Files download in the background. This method is better suited for larger files, such as those used in Intelligent Content.
                • Cache: Files download on demand when sales reps preview or use them. This method is better suited for smaller, more numerous files, such as Field Email templates.
              9. Enter the SOQL filter condition to generate metadata filtering data for the object using the simple editor or advanced editor.
                Note
                Note

                Enter only the conditional logic, not a full SOQL statement. The WHERE clause is implied, so don’t include the WHERE keyword or any other SOQL keywords. The SOQL filter also supports dynamic variables for dedicated data access.

                If you don’t enter a SOQL filter condition, metadata is generated for all rows of the selected object. Filters supplement existing record-level sharing and apply only to data sales reps already have access to. If an object’s sharing model is Private, sales reps download only the records they can access through ownership or sharing. If an object’s sharing model is Public, use filters to limit downloaded data, optionally.

              10. Save your changes.
            5. Before you generate the metadata cache, validate the object metadata configuration records to prevent failures and to make sure they’re set up correctly.
              1. Select one or more object configuration records that you want to validate.
              2. Click Validate.
                A notification confirms that validation is queued.
                Note
                Note Cancel an in-progress validation by clicking Abort, and then click Yes in the confirmation window to proceed.
              3. To monitor the validation status, click the link in the notification.
              4. To track the progress later, go to Setup, find and select Application Test Execution, and look for the latest run of lsc4ce.DbSchemaValidatorTestSuite.
                After the validation is complete, the configuration status changes to Valid.
            6. Assign Profiles to Object Metadata Configuration.
              1. Select one or more configuration records you want to assign to a profile.
              2. Click Assign.
              3. In the Select Assignment window, select Profile as the assignment type.
              4. Select a profile.
              5. Click Submit.
              6. To verify the assignment, click View Assignments in the object configuration record actions.
                You can also edit a specific object configuration record and view the selected profiles.
            • Dynamic Variables for SOQL Filter Conditions
              Use dynamic variables in the SOQL filter condition field to generate metadata filtering data customized to each user. Life Sciences Cloud replaces these variables at runtime with the appropriate user or territory values, enabling dedicated data access without hardcoding values.
            • Create SOQL Filter Condition Using Simple Editor
              Use the Simple Editor to build basic SOQL filter conditions for object data. The Simple Editor guides you through assembling condition logic and supports dynamic variables.
            • Create SOQL Filter Condition Using Advanced Editor
              Use the Advanced Editor to create SOQL filter conditions for object data by directly typing your filter logic. The Advanced Editor also supports dynamic variables and enables you to test your SOQL condition before saving.

            See Also

             
            Loading
            Salesforce Help | Article