---
schema_version: "1"
id: e4b2d81047f58df16d6c24add98730dd5933a0c1cceefa30e7b89fabd40bb660
title: Data Extension Considerations for Data 360
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_data_extensions.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_data_extensions.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: bdf3a5d28baf30703e1dc5d9745a78ef1e5059714523521232a128bdfcf7e3ce
description: If you ingest a data extension into Data 360, you should be aware of some core functionality within Marketing Cloud Engagement and how they operate within Data 360.
products:
  - Data 360
release: "264"
---
# Data Extension Considerations for Data 360

If you ingest a data extension into Data 360, you should be aware of some core functionality within Marketing Cloud Engagement and how they operate within Data 360.

## Structure

In Marketing Engagement, orgs are divided into business units, which is the hierarchical structure that controls role-based access to data.

Data extensions can belong to one business unit, multiple business units, or they can be shared across business units.

To view a data extension, select an associated business unit in the context filter dropdown. The business unit dictates the cascaded folder hierarchy.

## More Considerations

- After data extension configuration, don't change the schema. Data 360 doesn't support schema changes.
- You can only request one data extension at a time.
- Date field types in data extensions appear in YYYY-MM-DD format in Data 360.

#### See Also

- [_Salesforce Help_: Data Extensions with Enhanced Subscriber Features in Marketing Cloud](https://help.salesforce.com/s/articleView?id=mktg.mc_es_de_enhanced_subscriber.htm&type=5&language=en_US)
- [_Salesforce Help_: Data Extensions in Contact Builder](https://help.salesforce.com/s/articleView?id=mktg.mc_cab_data_extensions.htm&type=5&language=en_US)