From 8d0195f7574ccebd00ba21e59ca17fd56b3be8b7 Mon Sep 17 00:00:00 2001 From: prigiattiperrut <47340158+prigiattiperrut@users.noreply.github.com> Date: Thu, 30 Jan 2025 18:28:23 +0000 Subject: [PATCH 1/2] Update destination-data-control.md --- .../sources/schema/destination-data-control.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/src/connections/sources/schema/destination-data-control.md b/src/connections/sources/schema/destination-data-control.md index 0705092a98..3fe4f6edd2 100644 --- a/src/connections/sources/schema/destination-data-control.md +++ b/src/connections/sources/schema/destination-data-control.md @@ -67,7 +67,16 @@ To download a Source Schema CSV file: 6. Once the file status column indicates that the download was successful, click the **Download CSV** link to download your CSV to your computer. If the file status column shows that the download has failed, return to the Source Schema page and try the download again.
The Source Schema CSV name has the following format:
`workspaceSlug-sourceSlug-schemaType--yyyy-mm-dd--hh-mm-utc` > info "All events and properties are now included in the CSV file" -> When you export a Source Schema, all events and properties are included in the CSV file regardless of the filters or search parameters currently applied to the Source Schema view. +> When you export a Source Schema, all events and properties are included in the CSV file regardless of the filters or search parameters currently applied to the Source Schema view. + +## Understanding the Difference Between Schema UI and CSV Export + +When exporting a CSV from the Schema UI, it's important to note a key difference in how event data is structured: + +- In the Schema UI, all instances of a unique event name are grouped into a single row, regardless of the different properties associated with that event. +- In the CSV file, each unique combination of an event name and its tracked properties appears as a separate row. + +This behavior is intentional and provides greater granularity, allowing you to see how different properties are tracked for the same event. ### View download history From 8b46a846e28b26855d7e8d4a2bd54ed3e8c71a7b Mon Sep 17 00:00:00 2001 From: stayseesong <83784848+stayseesong@users.noreply.github.com> Date: Fri, 31 Jan 2025 14:25:02 -0800 Subject: [PATCH 2/2] Update src/connections/sources/schema/destination-data-control.md --- src/connections/sources/schema/destination-data-control.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/connections/sources/schema/destination-data-control.md b/src/connections/sources/schema/destination-data-control.md index 3fe4f6edd2..438fa3428f 100644 --- a/src/connections/sources/schema/destination-data-control.md +++ b/src/connections/sources/schema/destination-data-control.md @@ -69,14 +69,14 @@ To download a Source Schema CSV file: > info "All events and properties are now included in the CSV file" > When you export a Source Schema, all events and properties are included in the CSV file regardless of the filters or search parameters currently applied to the Source Schema view. -## Understanding the Difference Between Schema UI and CSV Export +## Difference between Schema UI and CSV Export -When exporting a CSV from the Schema UI, it's important to note a key difference in how event data is structured: +When exporting a CSV from the Schema UI, there are differences in how event data is structured: - In the Schema UI, all instances of a unique event name are grouped into a single row, regardless of the different properties associated with that event. - In the CSV file, each unique combination of an event name and its tracked properties appears as a separate row. -This behavior is intentional and provides greater granularity, allowing you to see how different properties are tracked for the same event. +This allows you to see how Segment tracks different properties for the same event. ### View download history