Track Changes to Transformation Datasets with Version History
Track Changes to Transformation Datasets with Version History
Transformation-type Datasets now include a Version History on the Dataset Details page. Every time someone saves a change to a transformation Dataset, a new version is recorded with the date of the edit and the user who made it — giving your team a clear, auditable record of how a Dataset has evolved over time.
For SQL transformations, each version also includes tools to review the exact query at that point in time and see what changed relative to the previous version.
NoteVersion History is only available on transformation-type Datasets. It is not shown on ingested or native-provider Datasets.
Where to find Version History
- Open Data Cloud and navigate to the Dataset you want to inspect.
- Open the Dataset Details page for that Dataset.
- Scroll to the Version History section.
Each row in Version History represents one saved version of the Dataset, ordered from most recent to oldest.
What's in each version
| Column | Description |
|---|---|
| Version # | The sequential version number assigned to each save. Version 1 is the earliest recorded version; the most recent save carries the highest number. |
| Edit Date | When the version was saved. Shown in your browser's local timezone. |
| Edited By | The name of the user who saved that version. Email domains are stripped — the column displays just the user's name (e.g., jane.smith rather than [email protected]). |
| View SQL | (SQL transformations only) Opens the full SQL query for that version in a read-only viewer. |
About "Edited By" on older versions"Edited By" is captured starting with the May 8, 2026 release. Versions saved before the feature shipped will show a dash (
—) in the Edited By column because that information wasn't recorded at the time.
View the SQL for a past version
For SQL transformation Datasets, you can open the exact query that was in effect for any version:
- In Version History, find the version you want to review.
- Click View SQL on that row.
- A read-only modal opens with the full SQL query.
- Use the copy-to-clipboard button to copy the query — handy for pasting into a scratch workspace, sharing with a teammate, or adapting into a new transformation.
The viewer is read-only. Opening a past version's SQL does not change the Dataset or roll it back.
Compare SQL between versions with Diff
When you open the SQL viewer for a version, you'll also see a Diff tab. The Diff tab highlights line-by-line changes between the selected version and the version that came immediately before it.
- Added lines are highlighted to show what was introduced in this version.
- Removed lines are highlighted to show what was taken out from the previous version.
- Unchanged lines are shown for context so you can read the change in place.
Use Diff to quickly answer questions like:
- "What changed in this Dataset between last week and today?"
- "Which join or filter was added in the most recent edit?"
- "Did this refactor actually change the logic, or just the formatting?"
NoteThe Diff tab is available only on SQL transformation Datasets. The earliest recorded version has nothing to compare against, so its Diff tab will be empty.
Common use cases
- Audit changes. See who edited a transformation Dataset and when, without digging through Slack or change-management tickets.
- Troubleshoot downstream reports. If a report's numbers shifted, use Version History to identify when the upstream transformation changed and what changed in the SQL.
- Onboard teammates. Walk new team members through how a Dataset has evolved, with the full SQL history as reference.
- Review before rolling forward. Compare the current SQL against prior versions before making your next edit.