A new Auto-map comparison strategy option has been introduced to improve column mapping between SQL and EBX. Users can now configure how the add-on compares EBX fields with SQL columns by selecting from case-sensitive or case-insensitive strategies based on labels, names, or a combination of these with data types. This enhancement allows for more flexible and accurate automatic mapping behavior when importing from, or exporting to an SQL data source.

The ability to download records that include invalid data and were not imported has been added to the Import SQL service. The downloaded records are provided in a CSV or Excel file, depending on the administrator’s configuration. This feature helps users quickly locate and correct errors in the failed records. Edits can be made directly in the downloaded file, which can then be re-imported to insert the repaired records. The download link appears only after an import operation if one or more records could not be imported due to validation errors. Administrators can enable this feature in: Administration > Integration > TIBCO EBX® Data Exchange Add-on (New) > Additional configuration > Default option values > Import/Export table (SQL). Administrators can also define the file format (CSV or EXCEL) for the download.

The import simulation feature is now available when using the Import SQL service. This allows users to find and fix issues before importing. By default, you can download a file that includes records flagged with the following during the import simulation: import blocking errors, record blocking errors, non-blocking errors, warnings, or information-level messages. Administrators can enable/disable download of the simulation results file in: Administration > Integration > TIBCO EBX® Data Exchange Add-on (New) > Additional configuration > Default option values > Import/Export table (SQL).

The Combine multiple fields transformation function now accepts input from multi-valued complex groups during export operations. When used in combination with the option to Output to multiple target records, this functionality allows you take an object like an address group and export values to separate records. This is particularly useful when exporting to an SQL data source that does not support multi-valued fields.

The option to Include computed values has been added to the Export Excel service when run from the dataset level. For any existing templates, this option will default to enabled.

Export operations initiated at the table level now respect the active EBX® view of the table. Only fields visible in the selected view will be included in the exported output. This allows users to control the scope of exported data by configuring views to include only relevant fields. Dataset-level exports remain unchanged and continue to include all fields by default. Metadata fields from EBX®, such as creator, last updater, and Team Up ratings or comments, can now be exported—provided they are included in the selected view.

When exporting, the Result page now includes detailed statistics about the export operation. This ensures a consistent experience whether the operation is run as a background task or in real time.

The following enhancements have been made to improve clarity and consistency in labels across import-related screens:

A warning should be displayed when importing Excel or CSV at the dataset level when a user does not have permission to delete a record and the Import mode is Replace all content or Delete only.

The text in the UI for import, export, and transfer modes does not display correctly

The tooltip text for cross reference transformation functions is not correct.

An error occurs when exporting to Excel or CSV when related data is missing in an associated table.

After loading an older template that contains a transformation function, and navigating to the mapping screen, the mapping screen is blank. Additionally, the Back to options and Simulation buttons are unresponsive.

The mapping screen should be blocked for users when: creating a new record is disabled, and the target table primary key is hidden.

During a dataset level import, if table permissions are set to Read-only, users cannot access the mapping screen by deselecting the read-only table.

An issue occurs when exporting a foreign key label.

An issue is preventing the mapping screen from displaying.

The dataset label should display when transferring data between datasets.

An incorrect error message for invalid records is displayed on the result screen.

An incorrect error message is displayed when: Import mode is set to Update or Insert, Force import is enabled, and record permissions are disabled for creating a record.

An error occurs on a string concatenation transformation function when it is applied to fields that can contain empty values.

A JNDI data source cannot be configured when EBX® is deployed on a WebLogic, or JBoss server.

When using a cross reference function during import, and the data source's configured lookup field contains missing or empty values, the add-on creates duplicate records.

Fonts are no longer shipped with the JDK 11. Font rendering in Java 11 JVMs now uses pre-installed operating system fonts. This can cause issues in Linux environments when exporting Excel files. As a workaround, you can install the fontconfig package.

When exporting a view that includes EBX® metadata fields and Include computed values is disabled, the metadata fields do not display in the mapping screen and are not exported.

In rare cases, and Excel export that includes multiple transformation functions applied to multi-value complex groups with many levels can cause EBX® to freeze.

When using the SQL export service and exporting to a PostgreSQL database, the option to export to a view is not supported.

When exporting to SQL with TDV, if any error occurs, the operation is cancelled.

Due to a limitation in Excel, long fields with the number data type display all numbers past the 16th place as a 0.

Importing and exporting SQL: Read and write is not possible with the Timestamp data type with MS SQL Server.

Configuring a schema using the JNDI configuration in your web server is not supported.

When creating a custom transformation function, you must use a predefined data type for its input and output fields.