What's new and changed in watsonx.data intelligence

watsonx.data intelligence updates can include new features and fixes. Releases are listed in reverse chronological order so that the latest release is at the beginning of the topic.

You can see a list of the new features for the platform and all of the services at What's new in IBM Software Hub.

IBM watsonx.data intelligence Version 2.3.1

A new version of watsonx.data intelligence was released in February 2026.

This release includes the following changes:

New features

This release of watsonx.data intelligence includes the following features:

Add business context to document sets: You can now select an additional processing option for your unstructured data curation flows to enrich the generated document sets. If document content matches a data class in the selected scope, business terms and classifications that are linked to that data class are automatically assigned.
For details, see Designing unstructured data curation flows.
New data source for unstructured lineage import: You can now import unstructured lineage metadata from IBM Cloud Object Storage and visualize it on the lineage graph.
Visualize Unstructured Data Integration operators on the data lineage graph: When you visualize unstructured data on the lineage graph, you can now view individual operators within the flow. By reviewing runtime metadata and other details, you can better understand how each component contributes to the overall flow outcomes.

Manage relationships between governance artifacts and data quality assets on the governance rule level

You can now create and edit relationships between governance artifacts and data quality definitions or data quality rules on the governance rule level. Previously, you had to manage these relationships from the data quality definition asset or data quality rule asset view, which required edit permissions in production environments. Now, if you have the Manage data quality relationships permission, you can edit data quality rules and manage relationships.

For details, see Designing governance rules.

Generate plain language descriptions for data quality rules

You can now automatically generate clear, plain language descriptions for your data quality rules, whether they are defined by business logic or written in SQL format. Plain language descriptions can help all users understand, review, and trust the data quality checks that are applied to your data assets.

For details, see Managing data quality rules.

Import, enrich, and assess the quality of data from additional data sources

You can now import metadata from the following data sources, enrich that data, and assess its quality:

Amazon Aurora for MySQL
Amazon Aurora for PostgreSQL

In addition, you can now write analysis output to tables in IBM Db2 for i.

For details, see Supported connectors for discovery, enrichment, and data quality.

Publish data quality rules to catalogs

You can now publish data quality rules from projects to catalogs. After a data quality rule is published into a catalog, you can add it into other projects for reuse.

For details, see Managing data quality rules.

Enhancements to roles and asset privacy settings for data source definitions

You now create data source definitions as public assets by default in the Platform assets catalog. This change improves visibility into newly created data source definitions.

If you have the Viewer role in the Platform assets catalog, you can now see data source definitions on the Data source definitions tab.
If you have the Editor or Admin role and have the necessary permissions and privileges, the improved visibility makes it easier to configure data lineage correctly.
If you have the Viewer, Editor, or Owner role for a specific data source definition, you can now also see its endpoints.
For details, see Roles and asset privacy settings for data source definitions .

Visualize asset owners and collaborators in Relationship explorer

You can now display relationships between assets and their owners and collaborators, which highly improves collaboration, clarifies ownership, and accelerates issue resolution or data onboarding.

Resynchronize data in Relationship explorer

Administrators can now resynchronize data to ensure that the latest updates are displayed in Relationship explorer. The resynchronization is useful to quickly correct out-of-sync data issues. Additionally, when Relationship explorer is enabled in environments where large volumes of assets and governance artifacts already exist, running resynchronization indexes all data, which then can be discovered.

For details, see Resynchronizing assets and artifacts in the knowledge graph.

Display data quality rules and data quality definitions in Relationship explorer

You can now visualize relationships for data quality rules and data quality definitions in Relationship explorer, including relationships with business terms and governance rules.

Make custom properties and relationships mandatory

When you create a custom property or relationship definition for governance artifacts, you can now decide whether to make those properties mandatory. When adding or editing an artifact with mandatory properties, the user must provide all mandatory values before saving.

For details, see Custom properties, relationships, and asset types.

New data sources for lineage metadata import

You can now import lineage metadata from the following additional data sources:

IBM Data Virtualization
Informatica PowerCenter
Microsoft SQL Server Analysis Services (SSAS)
Microsoft Power BI Report Server (Microsoft Power BI Desktop)
Statistical Analysis System (SAS)
Talend

After the data is imported, you can visualize it on a lineage graph.

For more information, see Supported connectors for lineage import.

Connect to new data sources by using a new version of the Manta agent

You can now import lineage metadata from the following data sources by using an agent:

Apache Hive
Google BigQuery
Informatica PowerCenter
Microsoft SQL Server Integration Services (SSIS)
Qlik Sense

Additionally, a new agent version is introduced, 1.4.0. Versions 1.0.0, 1.1.0, and 1.2.0 are deprecated. Consider updating your existing agent instances to the latest version 1.4.0.

For more information, see Configuring agents for lineage metadata import.

You can now create assets from data sources that you use for lineage import

You can now create catalog assets by connecting to the following lineage-specific data sources:

InfoSphere DataStage
Informatica PowerCenter
Microsoft Power BI (Azure)
Microsoft SQL Server Analysis Services (SSAS)
Microsoft SQL Server Integration Services (SSIS)
MicroStrategy
Qlik Sense
Statistical Analysis System (SAS)
Talend

For more information, see Importing metadata.

Updates

The following updates were introduced in this release:

Data quality updates
- You can now add custom properties to the details section of data quality definition and data quality rule assets, for example, to gather lifecycle information.
- You can now define the job configuration for running your data quality rule when you create the rule.
You can now define term assignment rules for columns by referring to the name or description of the parent table of the column.
You can now select which columns to display in the catalog view not only in the asset listing grid, but also in the columns grid and Relationship table by clicking Manage columns on the catalog page. Also, the columns grid now includes a Display name column (the Generated AI name).
For details, see Manage columns for catalogs.
When you generate business terms, the Personal Information and Sensitive Personal Information classifications are automatically added where applicable. You can use these classifications to control groupings of assets in your company and protect highly sensitive data.
For details, see Generating business terms, Classifications, and Generating business terms.
Reporting updates:
- A new reporting table dq_rule_execution_definition_counts is now available for reporting on the number of records tested, passed and failed for a specified rule definition during the execution of this rule.
- When reporting on governance artifacts, you can now include version_number to report on the version of the specified artifact. The value defaults to 1 for backward compatibility.

When you create a metadata import job, you no longer need to select a data source definition before you can select a connection. You can now choose whether to define the data source definition or the connection first. If you select a connection that does not have a data source definition associated with it, you can create the data source definition directly in the metadata import wizard, based on the connection data.
When you view data on the lineage graph, you can now hide assets which are not connected to any other asset in the graph. By clearing the assets that are not relevant, you can better focus on your task.
When you import lineage metadata from IBM® Cognos® Analytics and IBM DataStage for IBM Cloud Pak for Data, you can now connect to any deployment type of these technologies that you can access over the network. When you configure the connection, you now specify a deployment type with the new required property.
When you view a complex lineage graph, you can now easily hide all child assets of a particular parent asset by using the Merge into parent option. Before you select this option, you can hover over the option name to see all of the child assets highlighted and see how many child assets there are. Merge the assets into the parent to display a more general view of your data.
When you view lineage, you can use the following new filters:
- Filter temporary assets, such as such as temporary data sets or temporary, global temporary, or volatile tables.
- Filter assets by quality score to identify data quality violations.
- Filter assets by users or user groups to easily determine ownership of assets.
You can now view SLA compliance on the column level on the lineage graph.
When the initial lineage graph is loaded, all parent assets are highlighted for better visibility.
The Microsoft.SSISODBCSrc component of Microsoft SQL Server Integration Services (SSIS) is processed and displayed on the lineage.
The Data Virtualization Manager stage of IBM DataStage for IBM Cloud Pak for Data is processed and displayed on the lineage.
The log files for IBM DataStage for IBM Cloud Pak for Data lineage import contain information about missing values in unresolved parameters.
The descriptions of Projects, Attributes, Facts, Metrics, Columns, and Logical Tables are now displayed as node attributes on the lineage for the MicroStrategy assets.
When you export the lineage graph to a PDF file, you can include metadata details in the exported file, such as description, tags, and others.

Customer-reported issues fixed in this release

For a list of customer-reported issues that were fixed in this release, see the Fix List for IBM Cloud Pak for Data on the IBM Support website.

Deprecated features

The following features were deprecated in this release:

Support for base document sets ends in a upcoming release.
Update any project archives that contain base document sets:
1. Import a project archive to convert base document sets to document sets.
2. Export the project again.

IBM watsonx.data intelligence Version 2.3.0

A new version of watsonx.data intelligence was released in December 2025.

This release includes the following changes:

New features

This release of watsonx.data intelligence includes the following features:

Curate unstructured data with a new tool

With the new unstructured data curation tool, you can now import and analyze unstructured documents, group these documents based on the analysis results, and process the documents further based on the grouping.

You set up an analysis flow where you import metadata, detect the format and the language of documents, and classify the documents based on predefined or custom document classes. As a second step, you set up a processing flow where you transform these grouped documents, generate entities and embeddings, and create document sets and document libraries that you can then use in your gen AI projects.

Results of an analysis flow in an unstructured data curation asset

For details, see Creating unstructured data curation flows.

The unstructured data curation tool replaces the unstructured data import and unstructured data enrichment tools. See the Unstructured data import, unstructured data enrichment, and base document sets deprecation notice.

Create SQL-based assets and data quality rules with text instead of SQL

Now you can describe the data asset or the data quality rule that you want to create in plain English and convert this text query into an SQL query. You can then run the generated query to create the asset or the rule.

Tech preview This is a technology preview and is not supported for use in production environments.

For details, see Creating data assets by using SQL queries and Creating SQL-based rules.

Disable certain generative AI capabilities for selected projects

Even if watsonx.data intelligence is installed with generative AI capabilities, you might not want to use these capabilities in all of your projects. You can now disable these capabilities per project. In projects where the capabilities are disabled, you can't work with natural language queries to create SQL-based assets and data quality rules. In addition, LLM-based name, description, or term generation and term assignment in metadata enrichment are disabled.

For details, see Restricting custom propertie.

Define catalog-specific custom properties for assets

You can now restrict custom properties for assets to a specific catalog. By using catalog-specific custom properties, you can more effectively display values that pertain only to selected domains and ensure that the right information is available to the right users.

To list custom properties that are restricted by a given catalog, use the sort by scope option and scroll down to the items for the catalog that you're interested in.

For details, see Creating data assets by using SQL queries and Creating SQL-based rules.

Manage columns for catalogs

You can now select which columns to display in the asset listing grid by clicking Manage columns on the catalog page. Select your columns, reorder them if necessary, and save your preferences to keep the information that is most relevant for you readily available. For example, you can modify the view to show you a list of assets with the display name, owners, and date added columns only.

Optimize term assignment

With the new tuning options for term assignment, now you can influence the weighting of term suggestions for better precision or recall.

For details, see Tuning options for term assignment.

Import primary keys and foreign keys and visualize them in Relationship Explorer

Import primary keys and foreign keys with metadata import instead of metadata enrichment. After import, you can access the associated relationships through the RHS panel and Relationship Explorer.

For details, see Advanced import options.

Versioning of governance artifacts

Track historical changes for the artifacts, schedule new versions to be published in the future, and restore or archive previous versions with the new Versions panel.

For details, see Versioning of governance artifacts.

Export data lineage to Collibra: You can now export data lineage and view it in Collibra. If you transfer lineage information into Collibra data governance platform, you can see a comprehensive view of your data flows and dependencies within your governance framework.
For more information, see Exporting data lineage to Collibra.
Starting parents are introduced in the data lineage graph: When you select an asset to be a starting asset in the lineage, all assets that are higher in the hierarchy are marked as starting parents. Also, all child assets of the selected asset are marked as starting assets. This distinction clarifies which assets are selected as the starting points for the lineage.

Disable data lineage for the unstructured data flows: Data lineage is generated for Unstructured Data Integration and unstructured data curation flows by default. You can disable the lineage generation for unstructured data to control when lineage is created.
For details, see Lineage for unstructured data.

Create and access data contracts in Open Data Contract Standard v3

Streamline your management of data contracts by using Open Data Contract Standard v3 (ODCS v3) format in Data Product Hub

Producers: You can now create data contracts in ODCS v3format. Create contracts from scratch or by using a predefined template.
Consumers: You can access and review data contracts directly in Data Product Hub or download them in YAML format, along with any associated test status information.

This optimized process enhances collaboration, ensures data quality, and enhances trust between producers and consumers.

For more details, see Managing data contracts.

Deliver data products from Microsoft Azure Databricks

You can now subscribe to a data product that is created in Azure Databricks by using the Access in Azure Databricks delivery method. Consumers can directly access Azure Databricks resources. After delivery of the data products, consumers see details on how to access the specific resources in Azure Databricks.

For more information, see Working with delivery methods.

Deliver data assets to a project by using the access in watsonx.data delivery method

You can now choose to import data product assets to a project by using the access in watsonx.data delivery method.

For more information, see Creating a data product from a project.

Manage and view data product reviews

Consumers can now create, edit, and delete reviews of data products. Producers cannot manage reviews.