https://bugs.kde.org/show_bug.cgi?id=463708
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=463708
--- Comment #15 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=463708
--- Comment #14 from alx.ku...@gmail.com ---
Created attachment 154977
--> https://bugs.kde.org/attachment.cgi?id=154977=edit
File with updated payee name from excessive 213 chars to reasonable.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=463708
--- Comment #13 from alx.ku...@gmail.com ---
First: what is the point to match a payee name having 213 characters?
I updated a sample file to have "Some Payee Name" and an import finished in
less than 2 minutes, well it is very slow, but not too
https://bugs.kde.org/show_bug.cgi?id=463708
--- Comment #12 from Giuseppe Fuggiano ---
Hi Jack,
thank you for your suggestions. Since there is no other solution, I think I
will end up preprocessing the CSV as you said.
Regards
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=463708
--- Comment #11 from Jack ---
First, I do not believe there is any way to match the Category on import. The
Category is set if the imported transaction is matched to an existing
transaction. If there is not already a wishlist for that, perhaps we can
https://bugs.kde.org/show_bug.cgi?id=463708
--- Comment #10 from Giuseppe Fuggiano ---
Hi Jack, thanks for your suggestion.
I can indeed import it as Memo, as it really is. But I also need to import it
as a Payee because I can't match the Memo field to determine the Payee (and
thus it's
https://bugs.kde.org/show_bug.cgi?id=463708
Jack changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=463708
Jack changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=463708
alx.ku...@gmail.com changed:
What|Removed |Added
CC||alx.ku...@gmail.com
--- Comment #7 from
https://bugs.kde.org/show_bug.cgi?id=463708
--- Comment #6 from Giuseppe Fuggiano ---
No sorry you should import it as follows:
first column: date
second column: amount
third column: payee
I'm using the third column as payee because I don't have the payee specified in
my CSV exported from the
https://bugs.kde.org/show_bug.cgi?id=463708
--- Comment #5 from Giuseppe Fuggiano ---
Hi, sorry for the few information provided. You imported my sample data as
expected. I'm using a "standard" setup, no network involved. My drive is
healthy. My PC is a DELL with 6 cores i7-8750H CPU @ 2.20GHz.
https://bugs.kde.org/show_bug.cgi?id=463708
Jack changed:
What|Removed |Added
CC|ostroffjh@users.sourceforge |
|.net|
--
https://bugs.kde.org/show_bug.cgi?id=463708
--- Comment #4 from Jack ---
What I will ask is what type of PC are you using? I just did import the csv to
a newly created XML file with one checking account. It accepted column 1 as
the date, column 2 as the payee, and column 3 as the payment
https://bugs.kde.org/show_bug.cgi?id=463708
Jack changed:
What|Removed |Added
CC||ostroffjh@users.sourceforge
|
https://bugs.kde.org/show_bug.cgi?id=463708
--- Comment #2 from Giuseppe Fuggiano ---
Created attachment 154945
--> https://bugs.kde.org/attachment.cgi?id=154945=edit
test data
Use this data file to reproduce the bug. I've imported it to a new XML file. It
tool more that 10 minutes to finish.
https://bugs.kde.org/show_bug.cgi?id=463708
Giuseppe Fuggiano changed:
What|Removed |Added
Platform|Flatpak |unspecified
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=463708
Jack changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
18 matches
Mail list logo
