You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
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
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.
The text was updated successfully, but these errors were encountered: