beatbesmer / data-importer Goto Github PK

Respect the with to create split-bookings, grouped bookings or single transactions (assign roles first)

So we also have to check if roles for Level-D data still should be selectable

Need to extract from the current camt.053 file

• Headers (Name of fields)
• Example Data (Real content from those fields)

Darft of TransactionModel exists, needs to be tested

Should the CSV options be reused? In camt, we can build unique keys by message and statement IDs, including some fields from level c and d...

Currently, there are only visible in the config-view... without any effect

• Keep options selected in the configuration
• Make fields in role-configurator visible depending of configuration
• Apply options selected to the extraction / conversion of camt.053 data
• Define customized config (data-importer\config\camt.php)

As with classes in app/Service/CSV/Converter

Some parts of FIDI which handles camt and CSV, still use CSV in their name.

Take the same roles as for an CSV or use another set of roles?

Some d-level values can override existing c- level values. Currently, as they share the role, there seems no guarantee in the data mapper, to get the correct value in the dataarray from the desired level

There arent the same options as with a CSV.

• There are no file-headers, no seperation of values etc.
• A default account is already defined in the CAMT-file
• Ad an unique key for transaction, there should be a special field. So Duplicate transaction could / shoud use this one
• ... and maybe some more