This release contains the following new features:
You can now import XLSM files.
An administrator can now define the default values used in import, export, and transfer operations.
The number of updated and skipped records is now included in the import and transfer service results summaries.
Statistics are now available when transferring data at the table level.
A new built-in transformation function is available that allows you to define different list separators for different fields.
Names, descriptions, and data types were added to the add-on's built-in transformation functions. These values are now read-only.
This release contains no updated to third-party libraries.
This release contains the following closed issues:
[DINT-4226] The template cannot be saved after changing and publishing the data model.
[DINT-4246] The cell function instead of the cell value is imported when importing Excel.
[DINT-4271] File names that include Chinese characters do not display correctly in exported CSV and Excel files.
[DINT-4307] A scheduled workflow job fails due to database connection issues.
[DINT-4417] The SQL template cannot be loaded when configuring the JNDI in the context.xml file.
[DINT-4435] A large dataset cannot be imported from Excel.
This release contains the following known issues:
[DINT-4339] A JNDI data source cannot be configured when EBX® is deployed on a WebLogic, or JBoss server.
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 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.