https://bugs.kde.org/show_bug.cgi?id=14
--- Comment #6 from Ralf Habacker ---
> If an operation is a duplicate, it has already been imported once. How can it
> change if it is imported a second time?
Before aqbanking 6.3.1, (paypal) transactions were imported without memo,
although there might be a memo, i.e. Aqbanking now provides more data than
before.
Since the duplicate check does not include the memo field, this change is not
detected and therefore this commit checks for the detected duplicates if the
memo field of the present transaction is empty and imports the memo field only
in this case. This is effectively a one-time attribute update of the memo
field.
> If this is only for paypal transactions imported with a previous version of
> AqBanking, I vote against it because it could affect other importers as well.
This functionality can in principle be extended to all aqbanking sources, but
requires that the aqbanking backend in question populates the memo field. If
the memo field is not filled by aqbanking, nothing happens.
> If you want to do this, remove the transaction in the general ledger and
> import it again.
That's what I did at first, but found out that if you have a large number of
transactions, this is very time consuming as you have to manually find and
delete all the transactions that don't have a memo in order to re-import those.
To give the user control over this process, an option could be added in the
online settings of an account to explicitly enable this feature.
--
You are receiving this mail because:
You are the assignee for the bug.
