[Bug] CSV Import Fails when no Column named "Date" is provided

[zeal0]

Describe the bug
I've been playing around with the CSV-Import feature with a CSV-Export created via my bank portal without adopting to the provided template specifics to save some time on the import procedure. As I'm situated in a non English-Speaking country my CSV-export and it's column titles are therefore not matching the expected Inputs.

I know this is against the intended usage, nevertheless I wanted to share this bug/my findings as I feel it would greatly improve usability for other affected users and even if a fix might not be possible, the workaround on the user's side is very easy to implement.

What I've discovered is that the import function is actually very forgiving in terms of deviating from the provided templates as the option to assign the columns to their matching values actually used by Cashew is provided after the import.
Nevertheless, there seems to be one specific issue related to the presence of a column literally named "Date".

If that column name is missing, the import will always fail on various errors (screenshots provided) depending on the name of the columns present - if I rename the corresponding date column header to "Date" the import proceeds without any issues.

I've additionally attached two Dummy CSV files - one with the headers as provided by my bank (generic data, not-sensitive) that will fail the import, and one with a renamed "Date" column that will pass the import.

Unaltered CSV:
DummyCSV_nodate_column.csv

Adjusted CSV with "Date Column:
DummyCSV_withdate_column.csv

How to reproduce
Import DummyCSV_nodate_column.csv in Cashew to provoke the error.
Import DummyCSV_withdate_column.csv in Cashew for a successful import.

Screenshots/videos
Error1:

Error2:

Details

• Device: Windows10 + Browser (Mozilla)
• App Version: v5.4.0+413, db-v46

Additional notes
I just wanted to add that the app in itself is absolutely fantastic and this is really just a minor inconvenience - keep up the great work!