Import uses configuration template 'default' by default.

[blackappsolutions]

Please provide a way to select the import-template as it is done in the export (https://github.com/CoreMedia/csv-reporting/blob/master/csv-studio/src/main/joo/com/coremedia/csv/studio/CSVExportDialog.mxml#L39) to synchronize both oprations.

[blackappsolutions]

Implemented poor-mans template-choosing for imports 7b3ace5
See #4

[kmcherni]

Hi Markus,

Yes - the original idea behind the templates was to have this functionality to define the custom names of your columns headers for both import & export. Although this part of the functionality fell out of scope of the initial implementation - this feature is still planned for future development.

While the import does use the default template mapping between column headers and properties - the export template feature still has its uses as you can define which columns you wish to report on. The importer will still ingest the report even if there are missing columns - with the exception of Content ID and Content Type - to ensure data integrity.

Please let us know if you have any further questions or concerns!

Thanks,
Kevin

[blackappsolutions]

Hi Kevin,

so what do you think of my solution? See #4

[blackappsolutions]

It is not so good as having a combo box, as it is a global setting, but better as nothing.

Do you see the chance implementing the combo box for imports?

[blackappsolutions]

We found a solution