Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does not correctly export transactions if '\n' is in the Description or Original Description column #55

Closed
bmusat opened this issue Dec 19, 2023 · 1 comment

Comments

@bmusat
Copy link

bmusat commented Dec 19, 2023

I've noticed that when exporting transactions from Mint, if there are any line feeds in the Description or Original Description fields in the .csv that it will not export properly. The fields are double quoted but the '\n' in those fields is not escaped properly and hence causes problems in the exported file.

@grablair
Copy link
Collaborator

grablair commented Jan 4, 2024

Hi @bmusat! This is a repository for a community-made python client to the Monarch API. We have no control over the API itself, the Monarch website, or any browser extensions Monarch provides to customers.

This sounds like a report of a potential bug in the Monarch Mint Exporter extension. To report such a bug to Monarch, you should use the "Help & Support" -> "Contact Support" option in the Monarch Website sidebar.


That being said, I can try and help best I can. I will be converting this into a discussion as it is not an issue with the code in this repository.

I just tried creating a transaction in Mint with the description "Test\nItem", which exported successfully using both the Mint website's "Export transactions" button, as well as the Monarch Mint Data Exporter extension. The result was:

"Date","Description","Original Description","Amount","Transaction Type","Category","Account Name","Labels","Notes"
"1/04/2024","Test\nItem","Test\nItem","123.00","debit","Shopping","Cash","",""

Which imported successfully on Monarch, so I am unable to reproduce the issue.

Are you receiving an error when importing the transactions into Monarch? If so, can you attach a trimmed CSV containing some of your problem transaction(s)?

Repository owner locked and limited conversation to collaborators Jan 4, 2024
@grablair grablair converted this issue into discussion #59 Jan 4, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants