Dear FirstSpirit product management,
currently we observe problems when importing a FirstSpirit project owning a relational DB-schema whose data structure has been modified. For instance, when:
- nullable fields have been switched to non-nullable columns
- etc.
and relational database content based before the structural change is part of the export result (here: contains "nullable" values), the import will fail. Up to now, it is manually necessary to modify:
- text files, here: database schema configuration settings and remove the "non-nullable" columns
or
- correct the already existing relational data content
To prevent doing these steps for each FirstSpirit project export, a feature request to fix that behaviour is urgently necessary.