The following features and enhancements were included as part of Data Bridge 26.10.
Improved delta exports
-
Data Bridge now identifies changes to parent records and their associated records using separate, parallel queries (DATABRIDGE-2200). This enhancement lowers the chance of query timeouts and improves the overall stability for delta snapshots that include association changes. Full snapshots and parent-only delta snapshots are unchanged.
-
Delta exports can now identify new or changed records using a configurable timestamp instead of always using the hard-coded
sysEditTimevalue, supporting data sources with alternative change-tracking timestamps (DATABRIDGE-2202). To use this capability, set thedeltaWatermarkAttributevariable in the subject area metadata to the desired timestamp attribute name, save the changes, and select Load Metadata in the Global Settings workspace.
Simplified configuration prefixes
Data Bridge configuration environment variables now use the bridge. and dng. prefixes instead of meta.bridge. and meta.dng., clearly separating application settings from the meta. prefix reserved for metadata-loading configuration (DATABRIDGE-426). Update your deployment configuration to use the renamed flags listed below.
|
Old variable name |
New variable name |
|---|---|
|
meta.bridge.crmHttpURL |
bridge.crmHttpURL |
|
meta.bridge.exportDirectory |
bridge.exportDirectory |
|
meta.bridge.isChunked |
bridge.isChunked |
|
meta.bridge.isDataIngestionEnabled |
bridge.isDataIngestionEnabled |
|
meta.bridge.isTombstoneDeleteEnabled |
bridge.isTombstoneDeleteEnabled |
|
meta.bridge.loadCRMMetadataViaAPI |
bridge.loadCRMMetadataViaAPI |
|
meta.bridge.pageSize |
bridge.pageSize |
|
meta.bridge.useDataSources |
bridge.useDataSources |
|
meta.bridge.useMultiTenant |
bridge.useMultiTenant |
|
meta.bridge.usePublishingTargets |
bridge.usePublishingTargets |
|
meta.dng.cloud.enabled |
dng.cloud.enabled |
|
meta.dng.enabled |
dng.enabled |
|
meta.dng.useNonPersistedAttributes |
dng.useNonPersistedAttributes |
To upgrade your deployment configuration:
-
Open the Data Bridge
.environmentfile in NexJ Studio or a text editor. -
Find all environment properties that have a name starting with
meta.bridge.and remove themeta.prefix from the name. For example, change themeta.bridge.exportDirectoryvariable tobridge.exportDirectory. -
Find all environment properties that have a name starting with
meta.dng.and remove themeta.prefix from the name. For example, change themeta.dng.cloud.enabledvariable todng.cloud.enabled. -
Save your changes and re-deploy Data Bridge.
CSV export improvements
Data Bridge CSV exports now use memory more efficiently and provide improved stability, reducing the risk of out-of-memory errors when exporting large datasets (DATABRIDGE-2197).
Security enhancements
-
The Log4j library has been upgraded to 2.26.1 (released by the Apache Software Foundation on June 3, 2026) (CRM-1611).
-
Apache Tomcat has been upgraded to version 9.0.122 (released by the Apache Software Foundation on September 15, 2026) (CRM-7144).