This release contains the following new features and enhancements:
A new option is available that bypasses any data model validation rules or constraints, and imports, or transfers data as is. This option can be used in a data management architecture that includes landing, staging, and master zones. If the same data model is shared across all zones, constraints could prevent data from successfully importing into the landing zone. Forcing the import or transfer provides a workaround to this issue.
Load performance was improved for the options screen in instances where many related tables are included.
Support for templates was added when using the SQL import or export services in workflows and perspectives.
To improve readability, the data model variant name display format was updated.
Previously, if the Delimiter field was left blank, the add-on automatically applied a default double-quote delimiter. This behavior was changed so that if left empty, no delimiter is applied unless data includes a special formatting character, such as a line break, or field separator. In these cases, the default double-quote delimiter is automatically applied.
The Apache Commons Compress library was updated to version 1.26.
This release includes the following closed issues:
[DINT-4970] The current logic to handle inserts and updates can impact customer defined triggers.
[DINT-5124] An error occurs when exporting Excel due to exceeding the browser's storage restrictions.
[DINT-5137] The Mapping screen is unresponsive when exporting at the dataset level with a large number of table mappings.
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.
[DINT-5113] 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 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.