If this file doesn't work as well we have to start looking at other reasons this might be happening. If it works, this means your .csv file has something that isn't present on the example file, which should narrow things down. This could be some extra line(s) before the header, wrong encoding, an extra space in the heading, etc.
@eitchtee commented on GitHub (Feb 6, 2025):
@andremohrmann try importing this file, and let me know if you get the same error
[andremohrmann.csv](https://github.com/user-attachments/files/18698220/andremohrmann.csv)
It has the same content you shared with me in the other issue. But in my instance it worked:
```
[2025-02-06 21:58:33] INFO: Starting import process
[2025-02-06 21:58:33] INFO: Starting import with 4 rows
[2025-02-06 21:58:33] INFO: Successfully processed row 1
[2025-02-06 21:58:33] INFO: Successfully processed row 2
[2025-02-06 21:58:33] INFO: Successfully processed row 3
[2025-02-06 21:58:33] INFO: Successfully processed row 4
[2025-02-06 21:58:33] INFO: Import completed successfully. Successful: 4, Failed: 0, Skipped: 0
[2025-02-06 21:58:33] INFO: Cleaning up temporary files
```
If this file doesn't work as well we have to start looking at other reasons this might be happening. If it works, this means your .csv file has something that isn't present on the example file, which should narrow things down. This could be some extra line(s) before the header, wrong encoding, an extra space in the heading, etc.
Then this seems to be an encoding error of the file I get from my bank. Edit: It's not UTF-8, it's UTF-8 with BOM...
I tried importing only the lines I shared with you and it worked.
Then I opened the original csv and just copied and pasted the full content into an empty csv file.
With that file, importing works flawlessly.
Probably nothing you can do in this case, I guess.
But if you want I can share the full csv I get from my bank with you.
Otherwise, I will just have to get used to the workaround and automate the "conversion" myself ;)
Edit: Setting encoding: utf-8-sig in the import yaml works.
Thanks for the help! Much appreciated.
@andremohrmann commented on GitHub (Feb 7, 2025):
Then this seems to be an encoding error of the file I get from my bank. Edit: It's not UTF-8, it's UTF-8 with BOM...
I tried importing only the lines I shared with you and it worked.
Then I opened the original csv and just copied and pasted the full content into an empty csv file.
With that file, importing works flawlessly.
Probably nothing you can do in this case, I guess.
But if you want I can share the full csv I get from my bank with you.
Otherwise, I will just have to get used to the workaround and automate the "conversion" myself ;)
Edit: Setting `encoding: utf-8-sig` in the import yaml works.
Thanks for the help! Much appreciated.
Then this seems to be an encoding error of the file I get from my bank. Edit: It's not UTF-8, it's UTF-8 with BOM...
One of those cases where it's close enough to not raise an error, but different enough to not work.
Edit: Setting encoding: utf-8-sig in the import yaml works.
I was going to tell you to try that, glad you figured it out.
@eitchtee commented on GitHub (Feb 7, 2025):
> Then this seems to be an encoding error of the file I get from my bank. Edit: It's not UTF-8, it's UTF-8 with BOM...
One of those cases where it's close enough to not raise an error, but different enough to not work.
> Edit: Setting `encoding: utf-8-sig` in the import yaml works.
I was going to tell you to try that, glad you figured it out.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @eitchtee on GitHub (Feb 6, 2025).
Originally posted by @andremohrmann in #41
@eitchtee commented on GitHub (Feb 6, 2025):
@andremohrmann try importing this file, and let me know if you get the same error
andremohrmann.csv
It has the same content you shared with me in the other issue. But in my instance it worked:
If this file doesn't work as well we have to start looking at other reasons this might be happening. If it works, this means your .csv file has something that isn't present on the example file, which should narrow things down. This could be some extra line(s) before the header, wrong encoding, an extra space in the heading, etc.
@andremohrmann commented on GitHub (Feb 7, 2025):
Then this seems to be an encoding error of the file I get from my bank. Edit: It's not UTF-8, it's UTF-8 with BOM...
I tried importing only the lines I shared with you and it worked.
Then I opened the original csv and just copied and pasted the full content into an empty csv file.
With that file, importing works flawlessly.
Probably nothing you can do in this case, I guess.
But if you want I can share the full csv I get from my bank with you.
Otherwise, I will just have to get used to the workaround and automate the "conversion" myself ;)
Edit: Setting
encoding: utf-8-sigin the import yaml works.Thanks for the help! Much appreciated.
@eitchtee commented on GitHub (Feb 7, 2025):
One of those cases where it's close enough to not raise an error, but different enough to not work.
I was going to tell you to try that, glad you figured it out.