Loading
Feature Disruption - Service Cloud VoiceRead More
Feature degradation | Gmail Email delivery failureRead More
About Salesforce Data 360
Table of Contents
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
          Mapping UDLOs to UDMOs

          Mapping UDLOs to UDMOs

          Workloads in Data 360 that consume unstructured data do so through unstructured data model objects (UDMOs). When you create a UDLO, you map it to a UDMO.

          The relationship between UDLOs and UDMOs can be 1:1 or N:1. In other words, each UDLO can be mapped to at most 1 UDMO, while multiple UDLOs can be mapped to a single UDMO.

          For example, consider that you’re referencing case recording data from multiple external blob stores. Three different UDLOs reference data from these three sources: CaseRecordingsFromAWSBucket1, CaseRecordingsFromAWSBucket2, and CaseRecordingsfromGCS. Because these sources are logically the same object, the individual UDLOs are mapped to one UDMO: CaseRecordings.

          UDMO Field Mapping

          Data 360 automatically creates the field level mappings between UDLOs and UDMOs because the schemas across the two objects are identical. When you create a new UDLO, you have two options.

          • Map the UDLO to a new UDMO.
          • Map the UDLO to an existing UDMO.

          View which UDMO a UDLO maps to in the data mapping section for the UDLO. When you create a UDLO, Data 360 assigns the category, Directory Table to the DLO. Field mappings between a UDLO to UDMO are read-only. You can’t review or edit field mappings between a UDLO and UDMO.

           
          Loading
          Salesforce Help | Article