Downloads

September 2026

This release adds effective dates to reference data tables, so a record can hold several versions, each valid for its own period. It also expands the API: you can now read data observability alerts and the findings behind them, look up pipeline jobs and datasets observed by pipeline monitoring, and create DQ dashboards.

Effective dates for reference data tables

Keep several versions of a reference data record, each valid for its own period, so a tax rate, a product code, or an exchange rate changes on the date it takes effect without overwriting the past. The table still shows one row per record, with the version that applies today, while the other versions stay available.

You can:

  • Enable effective dates on an existing table or while creating a table from a file, and map the Valid from and Valid to dates to existing attributes or let ONE add them.

  • Time travel through the published data to see what was valid on a specific date, including records deleted since.

  • Manage the versions of a record on a timeline: split, extend, or create versions, and close the gaps between them.

  • See inverted, overlapping, or missing dates flagged as you edit, so you can fix them before they block publishing.

Tables that reference a table with effective dates always use the version that is effective today.

For details, see Use Effective Dates.

Monitor data observability alerts via the API

Integrate data observability alerts into the tools your team already uses. The public API now lets you read alerts, the findings behind them, and the assets they affect.

You can use the API to:

  • Forward alerts and their findings to ticketing, incident management, or reporting systems, and keep them in sync by polling for changes.

  • Drill down from an alert to its findings and identify the affected catalog items, pipeline jobs, and datasets.

  • Look up the pipeline jobs and datasets observed by pipeline monitoring, and map observed datasets to catalog items.

The API is read-only. To resolve or escalate an alert, or to configure who gets notified, use the web application.

For details about alerts, findings, pipeline jobs, and datasets, see the API documentation.

Create DQ dashboards via the API

Automate your DQ dashboard setup. The Data Quality API now lets you create a dashboard over selected DQ monitors, publish it, and retrieve or list dashboard configurations.

Use the API to:

  • Create dashboards from scripts or CI/CD pipelines, as the last step after setting up the monitors they aggregate.

  • Recreate existing dashboards in another environment, or from a previous Ataccama ONE deployment.

The API returns the dashboard configuration only, not its aggregated quality. You can view the aggregated quality and its breakdown in the web application, and each monitor’s DQ evaluation results stay available through the API.

For details, see Data quality dashboards.

Was this page useful?