Bug 440844 - It should be possible to assign more than one StatementKey to an account
Summary: It should be possible to assign more than one StatementKey to an account
Status: REPORTED
Alias: None
Product: kmymoney
Classification: Applications
Component: importer (show other bugs)
Version: 5.1.2
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-08-10 17:55 UTC by Dawid Wróbel
Modified: 2021-09-12 17:57 UTC (History)
0 users

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 Dawid Wróbel 2021-08-10 17:55:27 UTC
SUMMARY
When importing a statement, KMM checks if the account key, as provided by the importer, matches any account number or any account's StatementKey property. If none is matching, it then asks user to choose one by hand and sets the StatementKey value, so that in the future it can find the account automatically. 

However, the same account can be referenced by different IDs, depending for example on whether the statement was generated for a Checking Account or a Credit Card. Another use case is using different format, e.g. OFX and CSV.

STEPS TO REPRODUCE
1. Import a statement that references an account A formatted as A'
2. Assign A' to an existing account A
3. Import another statement that references account A formatted as A"
4. Assign A" to the same existing account A
5. Import another statement that references an account A formatted as A'

OBSERVED RESULT
KMM will ask again to manually find the A' on the list of account, despite having previously done so.

EXPECTED RESULT
KMM should remember both A' and A" as valid StatementKeys for the account A and not bother user anymore.
Comment 1 Dawid Wróbel 2021-08-10 17:57:45 UTC
Additionally, the previously stored account keys should be listed on account's properties and be editable.