Released: June 2022
This release contains the following new features:
You can now export a table view. When you choose to export a view, only records contained in that view are exported. For example, if you have a view that filters and displays records that have a particular country code, only these records are included in the export operation. This option is available from the main Configuration page when exporting to CSV or Excel format at the table level. It is available from the Mapping table page when exporting at the dataset level.
When moving data via import, export, or transfer, the add-on logs were enhanced to include the following:
Dataspace name formatted as: the dataspace identifier (Dataspace label) (E.g. Reference (Master Data- Reference).
Dataset name formatted as: the dataset unique name (Dataset label) (E.g. Employee (Human Resources) .
Table name formatted as: the table path (Table label) (E.g. /root/Employee (Human resources).
User information.
The executed service name.
Upload:
Start of upload and completion percentage with a maximum of 10 lines. (E.g. Uploading 10%, 20%...).
End of upload notification.
Import, export, and transfer:
Start of operation and completion percentage with a maximum of 10 lines. (E.g. Processing data import 10%, 20%, 30%...).
End of operation notification.
IP address & HTTP session ID.
This release contains no functionality changes.
This release contains no changes to third-party libraries.
This release contains the following closed issues:
[ADIX-3558] Import returns an empty String instead of null for a String field if the value is missing in the imported file.
[ADIX-3559] All records are exported and transferred from a hierarchy view that has one record selected.
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.