All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
- Fixed custom attribute mapper screen (
isRequiredColumn
error) (#159)
- support for required and optional columns:
isRequiredColumn
inImportAttributeMapper
- Ignore
@Transient
properties in the import process (might be breaking change in some situations)
- CUBA 7.2.x
- Apache POI 4.1.1
- Improved Date Parsing Error Handling
- Data Import fails with Unique Configuration: Update and association attribute binding (#151)
- support for additional datatypes:
LocalDate
,Long
in parsing values
- CUBA 7.1.x
- DataImportAPI does not allow to use Excel files to be imported (#144)
- Exceptions are caught globally in GenericDataImportService and store it in the import execution instance
DataImportAPI
which provides an API of the application component for the core module. It allows to import FileDescriptor instances.- Ability to define the charset of the file to import (UTF-8 default)
- Data imports are logged and persisted for identifying what data failed during import process (
Administration > Data Import > Import Execution
)
- Exception during Import Wizard with saving unique configurations (#138)
- Support for CUBA 7 based Lookup screens via
WithImportWizard
interface (see README for more details) (#135) - dynamic default values support (#123)
- CUBA 7.0.x
- CUBA 6.10.x
- new UniquePolicy option: Abort. Will abort the complete import process immediately (#122)
- allowed different lookup column types for association types (Enum & all simple types) (#129)
- Fixed missing attributes PostgreSQL init db scripts
- Fixed syntax error in PostgreSQL init db scripts (#117)
- Support the ability to configure advanced import view configurations (#112)
- empty rows will be excluded from import (#106)
- check if the uploaded file in the in import wizard matches structure of the pre-defined import configuration (#78)
- correct SQL update scripts for MySQL & PostgreSQL (#103)
ImportAttributeMapper.dynamicAttribute
was removed. Was replaced withAttributeMapperMode
in 0.4.0
- CUBA 6.9.x
- start import wizard from every screen (
@WithImport
Annotation) (#33) - start import wizard from from import Configuration screen (#32)
- option to go steps back in import wizard (#71)
- BREAKING: make entity attribute selectable in import wizard (#24)
This change requires to manually go through the existing import configurations and adjust the "Entity attribute"
through the help of the new UI.
ImportAttributeMapper.entityAttribute
now only stores direct attribute names (not a full path liketeam.code
but rather onlyteam
)ImportAttributeMapper.associationLookupAttribute
is new and stores the Lookup attribute in case of an association (code
from the example above)ImportAttributeMapper.dynamicAttribute
is no longer usedImportAttributeMapper.attributeType
is new and stores the type of attribute: direct, reference or dynamic The adjustments can also be done manually through the entity inspector by changing the above mentioned attributes accordingly.
- ignore case for enum import (#77)
ImportAttributeMapper.entityAttribute
is no longer mandatory. In case it is not configured correctly, the column will not be imported and a corresponding log message will be created. This leads to less user facing errors in the import wizard.
- ORACLE DBMS support (has not worked anyways)
- DbHelper
- Import file types: JSON support
- Import file types: XML support
- default Binding: BigDecimal supported
- Unique Configurations
- Pre-Commit Script
- Import Transaction Strategies: Single transaction, Transaction per Entity
- Oracle DBMS support
- PostgreSQL DBMS support
- MySQL DBMS support
- Import Wizard
- supported file types:
.csv
,.xlsx
- Import Configurations
- Import execution logs
- CUBA 6.8.x