Skip to main content
Feedback

Data Integration Release Notes for May 2026

May 26 2026

Targets

New
We added these features

Snowflake

  • Merge is now the default loading mode for new data flows, replacing Switch-Merge. The Merge loading mode upserts data and automatically evolves the target schema, preserving Snowflake time travel, table identity, and failsafe continuity on every load. This change also applies to existing data flows using Merge loading mode. For more information, refer to Snowflake as a target.
  • Snowflake target loads using Merge loading mode no longer require SYSADMIN privileges at runtime. All load operations run under a dedicated role, BDI_ETL_ROLE, and SYSADMIN is required only once for the initial role and user setup. For more information, refer to Snowflake as a target.

May 21 2026

Blueprint

New
We added this feature
  • The Blueprint connector now supports multi-report configurations. You can configure, run, and map multiple reports within a single Blueprint connection, with report-specific settings managed independently for each report. For more information, refer to Report parameters.

May 14 2026

Sources

New
Source-to-Target Data Flow new experience enhancements

Coupa

  • We’ve expanded the new Source-to-Target data flow experience to support Coupa as a source. For more information, refer to Coupa connector.

Troubleshooting Agent

New
We added this feature
  • The Troubleshooting Agent now includes thumbs up and thumbs down buttons on each response, enabling you to rate the quality of the agent's suggestions. For more information, refer to Troubleshooting agent.

May 11 2026

Sources

New
We added these features

Jira

  • The Jira connector includes the following improvements:

    • Field selection: When running an Issues report, you can now select specific fields to include instead of returning all fields by default, giving you more control over the data pulled from Jira.
    • Pagination efficiency: Pagination for Jira Server instances is more efficient, reducing the number of API calls required for large data syncs.

    For more information, refer to Jira walkthrough.

SFTP

  • The SFTP connector now includes a configurable Auth Timeout (seconds) field in the connection settings. Use this setting to increase the authentication timeout when connecting to SFTP providers that are slow to respond. For more information, refer to SFTP connection.

Mixpanel

  • The Mixpanel connector now uses the Export API and Query API for data extraction, replacing the deprecated JQL API. This update ensures continued access to raw event data and multi-segmentation reporting. For more information, refer to Mixpanel walkthrough.
  • The Google Ad Manager connector now supports Interactive Reports through a new Interactive report tab. For more information, refer to Google Ad Manager connection.

Facebook Ads

Deprecation notice:

  • Meta is removing the Nielsen DMA breakdown from all Facebook Ads reporting solutions on June 22, 2026. If your data flows use the DMA breakdown option, they will stop returning data after this date.
    • What you need to do: Replace the DMA breakdown with Comscore Market in your Facebook Ads data flow configuration before June 22, 2026.
    • The Facebook Ads connector will be updated to add the Comscore Market breakdown option once Meta makes it available in the Insights API.
Fix
We fixed these issues

NetSuite Analytics

  • The NetSuite Analytics connector now runs SQL queries reliably, resolving intermittent failures that returned a RVR-NEA-106 syntax error despite the queries being valid.

Azure Blob Storage

  • The Azure Blob Storage connection test now correctly rejects invalid credentials, preventing incorrect configurations from being saved as valid connections.

May 10 2026

Sources

Fix
We fixed this issue

PostgreSQL

  • To prevent data loss during replication, REPLICA IDENTITY FULL is now required on PostgreSQL tables that contain large column types (TEXT, JSONB, or BYTEA) or have no primary key or unique index. If a table does not meet this requirement, data flow activation fails and the error identifies the table by name. To set up replica identity before activating your data flow, refer to Configure replica identity for selected tables.
On this Page