Released: September 2022
This release contains no new features.
This release contains no functionality changes.
The Apache POI library was updated to version 5.2.2.
This release contains the following closed issues:
[ADIX-3501] When using Dynamic Data Modeling, fields in the Excel sheet are generated under the wrong table.
[ADIX-3537] [API] Notify users when an unsupported import mode is specified.
[ADIX-3572] An error message lacks information after choosing to download the file containing invalid data during an Excel/CSV import operation.
[ADIX-3581] Data under a multi-value group field is exported incorrectly when this group contains a multi-valued child field.
[ADIX-3586] Excel file cells are incorrectly formatted when exporting numeric fields.
[ADIX-3609] A multi-value complex data type group is not exported when exporting to Excel with the Export related data mode.
[ADIX-3610] The column header is not correct when exporting the label for a Dynamic Enumeration with a Null or Empty value.
[ADIX-3622] The link to download a file with invalid data is not displayed when importing Excel or CSV with all import modes except Update or insert.
This release contains the following known issues:
Association object and selection node are not supported.
Data lineage.
Graphical view of the data mapping configurations.
Split of string transformation function is not supported for a multi-valued string field.
Data transfer between complex terminal nodes is possible only if they use the same Java Bean.
You can not export data from multiple complex nodes in EBX® that when there is at least one complex node with multiple occurrences.
You can not import data from multiple complex nodes in an XML file when there is at least one complex node with multiple occurrences.
Split of data works for terminal nodes only.
SQL export:
You can only export data from EBX® to the selected columns in the same tables of a view which is joined by multiple tables.
The add-on doesn't support exporting SQL with the Replace all content mode to a view which is joined by multiple tables.
Checking mandatory fields of a view in SQL database is not supported.
The export still executes normally and shows an error message from database when no privilege granted.
Exporting data from multi-valued fields and multi-valued groups is not supported.
You can not export data from EBX® to a view in PostgreSQL database.
Exporting data from EBX® to an auto-increment column in SQL Server is not supported because the IDENTITY_INSERT property is always set to OFF.
SQL import: Checking privileges for a view in PostgreSQL is not supported.
Dynamic data modeling: Foreign key statements in the DDL file are not managed.