Data Object Concepts and Schema in Data 360

During ingestion, Data 360 retrieves a sample of your data and recommends a source schema. You can then review and modify the recommended schema.

In the schema, the non-editable header label identifies the source of the raw data. You can change the other labels.

• Field Label—A proposed Data 360 display name for each source header column.
• Field API Name—A proposed Data 360 API name for each source header column.
• Data Type—A suggested data type for each source header column. For information on supported data types, see Data Types in Data 360.
  

  Warning If you select the wrong data type, you must delete the data stream and re-create it. You can’t change a data type after the data stream is created.

• Source, Object Name, and Object API Name
  When ingesting a data set into Data 360, you must name the data set source.
• Category
  When creating a data stream, you must select a category or type of data found in that data stream.
• Primary Key
  To create a data stream in Data Cloud, select a primary key or unique identifier for that source. If a data source doesn't have a field that can be used as a primary key, create a composite key by combining two or more source fields using a formula field.
• Categorize Anonymous and Known Profiles
  During ingestion, a source profile is categorized as either anonymous or known based on the value in the Is Anonymous field on the Individual DMO in data streams. A source profile without that field mapped is always considered known. Add the mapping to differentiate between known and anonymous profiles.
• Organization Unit Identifier
  The Organization Unit Identifier is an optional field that allows you to specify business units in your Data 360 data.
• Data Lineage Fields
  Data 360 adds fields to a data object to capture data source details.
• Source Object Schema Modifications
  You can modify Data 360 source object schema on the Data Stream details page. All changes are applied to future data imports. To apply logic retroactively, pull from the source and ingest into Data 360.
• Fully Qualified Keys
  Use Fully Qualified Keys (FQK) to avoid key conflicts when data from different sources are harmonized in the Data 360 data model.
• Create a Formula Field
  When you create a Data 360 data stream, you can choose to generate more fields. These supplemental fields can be hard-coded or derived from other fields in the data stream.
• Formula Expression Use Cases
  These examples show use cases of formula expression functionality in Data 360.