Version 3.98.2-svn1156574 I'd imported an investment transaction containing a valid, but incorrect, price. On correcting the file and reimporting, the old, incorrect, price was kept and the new, correct, price was discarded. Perhaps a warning should be given, or a query raised as to what action should be taken? Conversely, when manually adding a new price, if the same date is entered as an existing price, the old price is over-written without warning. It could be that the same date was entered by mistake, and that the existing price should not be over-written without warning.
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>