Summary: | Reimporting an investment transaction with different price does not get recorded | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | allan <agander93> |
Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
allan
2010-08-02 02:06:53 UTC
This it how it is designed: duplicates are discarded during import. In case you want to re-import a transaction you have to delete it before. Taking the price into the detection of a duplicate does not help you either: it would import a second transaction which is not what you want. I (partly) agree on the warning for the manual entry. In case you have a strong feeling we need a warning message, please enter a wishlist item here so that we can implement it. Don't forget to ask for a "Don't ask again" option. (In reply to comment #1) > This it how it is designed: duplicates are discarded during import. In case you > want to re-import a transaction you have to delete it before. Taking the price > into the detection of a duplicate does not help you either: it would import a > second transaction which is not what you want. > I've just double-checked, and I did delete before reimporting. However, deleting the transaction does not delete that price from the table. So the problem remains. > I (partly) agree on the warning for the manual entry. In case you have a strong > feeling we need a warning message, please enter a wishlist item here so that we > can implement it. Don't forget to ask for a "Don't ask again" option. In both cases, the result is not the expected result, so I'm not sure I understand why you think the former is OK, while the latter is (partly) not. However, I am aware of the issue and can live with it. <BG> |