Bug 386087 - csv exporter triggers lots of error messages about invalid transcations
Summary: csv exporter triggers lots of error messages about invalid transcations
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: importer (show other bugs)
Version: 4.8.0
Platform: Slackware Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-22 22:26 UTC by r454942
Modified: 2022-12-10 05:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description r454942 2017-10-22 22:26:48 UTC
On version 4.8.0

Exporting my kmymoney Investment account to csv I get tens of error messages about invalid transactions. Example: "Transaction number '20' is missing an account assignment. Date '2015-12-15', Amount '27,59;'. Transaction dropped." The transaction seems to exist in the ledger, but not as 20th transaction. Everything looks normal with the transaction, the account assignment is there. But the transaction is not exported to the .csv file. Consistency check reports no error.

Reproducible: Always

Steps to Reproduce:
1. File -> Export -> CSV
2. Select Investment account and field separator
3. Select the file you wish to export
4. Error messages about invalid transactions occur

Actual results: Transactions missing in CSV output

Expected results: All Transactions should appear and no error message should be reported
Comment 1 Jack 2017-10-22 22:42:22 UTC
The transaction number is KMM's internal id for the transaction, and is not generally needed or seen by the user.  You can search for the transaction, but you need to type in the complete identifier, something like T000000000000000020.  That will at least confirm you have identified the actual transaction it is complaining about.

Can you provide more information about the transaction?  What type of transaction?  How many splits are there?  That means is there a single transfer of funds (such as to or from the investment account's brokerage account) or are there more transfers, such as for an interest or fee category?
Comment 2 r454942 2017-10-23 23:27:58 UTC
Hm, ist this identifier unique in the whole file or unique for the account only? Should I search in the "Text" field of "search transactions" or in the "Details" ->search this number?

When I search T000000000000000020 in the "Text" field I find a transaction in a different account. When I search in the Details->search this number I find nothing. When I search for Details->Invalid instructions I find nothing.

The Transaction in this example "Transaction number '20' is missing an account assignment. Date '2015-12-15', Amount '27,59;'. Transaction dropped." is a dividend payment. There are many dividend payments, some buys and one "add shares" in the beginning.
Comment 3 Jack 2017-10-24 00:31:01 UTC
The T transaction IDs are unique to your kmy file.  If you search on T000000000000000020 then that is the transaction the program is complaining about.  Does the amount of that found transaction match the amount of the one you had identified?  It may simply be coincidence.  

Note when the program says the transaction is missing an account assignment, that may actually mean it is missing a category, which are internally treated as accounts.  If you do the search, and then double click on the found transaction, it should display that transaction in the ledger of the account it thinks the transaction belongs to.  What are the details there?  Does anything seem strange about it?  

When you say it is a dividend transaction, that is simply a transaction you have identified with the same date and amount.  In fact, you might try searching on that date and that amount to see if you find other transactions.
Comment 4 r454942 2017-10-24 21:04:20 UTC
There is not a single complaint, there are a lot during the export procedure. They all have small numbers like 20, 17, 16 etc. And many occur several times, e.g. Transcation 17 is reported 4 or 5 times with different dates and amounts. Also the progress bar is dancing forward/backward during export.

When I search for the Transcations 16, 17 and 20 I find a single transaction for each of them as an "add shares" transaction in the very beginning of another invest account (not the one that I was exporting). These transactions need no categories and they have none.

When I search e.g. for the date and amount of all the transactions number '17' reported during export of the invest account then I always find a single transaction that matches in the exported investment account. These are dividend transactions. During export they are reported in ascending order with respect to date. And they are all around the year 2015, few 2014. The transactions are missing in the exported csv.

I used several versions of kmymoney during the years. Is it possible that a bug in an older version around the year 2015 caused these problems?
Comment 5 Jack 2017-10-24 23:49:46 UTC
I suppose it's possible, but I can't think of any likely cause.  What is odd that it reports the same transaction number with different dates and amounts.  Is it possible to create a small test file with a few transactions that show the errors, or does a new file always work without errors?  If so, then saving your file as an anonymous file and attaching that to the bug might help.  

https://docs.kde.org/stable4/en/extragear-office/kmymoney/details.formats.anonymous.html
Comment 6 Justin Zobel 2022-11-10 08:51:44 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 7 Bug Janitor Service 2022-11-25 05:18:58 UTC
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 bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2022-12-10 05:15:53 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!