Skip to content
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

CSV import: all date fields but the one specified are filled with the import date #1586

Closed
lucavallerini opened this issue Aug 2, 2018 · 7 comments
Labels
fixed Bugs that are fixed (in a coming release).

Comments

@lucavallerini
Copy link
Contributor

I am running Firefly III version 4.7.5.3

Following the import discussed in #1585, all transactions have all date fields except the date one filled with the import date. I noticed this yesterday on my first import. The transactions have only 1 date specified and during the import I set that date as the 'Date' field: this is filled correctly but for some reason all the other date fields are filled with the date of today.

@JC5
Copy link
Member

JC5 commented Aug 2, 2018

That is definitively a bug. I'll pick it up for the next release.

@JC5 JC5 added the bug label Aug 2, 2018
@lucavallerini
Copy link
Contributor Author

There is also another problem with this bug: I can modify those dates but I cannot remove theme.

@JC5
Copy link
Member

JC5 commented Aug 3, 2018

I've found both problems and they'll be fixed for the next release. 👍

@JC5 JC5 added the fixed Bugs that are fixed (in a coming release). label Aug 3, 2018
JC5 added a commit that referenced this issue Aug 3, 2018
@lucavallerini
Copy link
Contributor Author

Thanks, I applied the fix and now I can remove those dates.

@lucavallerini
Copy link
Contributor Author

lucavallerini commented Aug 3, 2018

Since I imported over a hundred transactions I also messed directly with the DB to erase all those dates. I used this query:

DELETE FROM `journal_meta` WHERE `name` IN('book_date', 'process_date', 'due_date', 'payment_date', 'invoice_date', 'interest_date') AND `created_at` >= '2018-08-01' 

This should be enough, right? It does not seem I have broken something but you now the DB better than I do.

@JC5
Copy link
Member

JC5 commented Aug 3, 2018

That should work just fine!

@JC5
Copy link
Member

JC5 commented Aug 7, 2018

I'm closing this since it's fixed. Look for this feature in the next release, and let me know if you encounter any problems!

@JC5 JC5 closed this as completed Aug 7, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jan 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
fixed Bugs that are fixed (in a coming release).
Projects
None yet
Development

No branches or pull requests

2 participants