---
schema_version: "1"
id: 1e208f4f52766eca983b906c81683fb07afd607150c0c3483ff499bca4d0d513
title: Mapping UDLOs to UDMOs
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_unstructured_data_map_udlo.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_unstructured_data_map_udlo.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 0e85adf72a16134c1fd73e4bd72d38492e9e9d034d17d9127be2f579112b91dd
description: 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.
products:
  - Data 360
release: "264"
---
# 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.