Transaction View issues when editing transactions (duplicate entries)

Dear PP Forum,

first of all thank you for your support and all the great work that went into this tool!

I have been having issues with the Transaction window (e.g. showing all transaction in deposit and security accounts) when editing transactions.

When I edit a transaction directly in the list of all transactions (for example the date and time), the row I edited ends up in the new location where it should be according to the sort order, but at the same time stays in the current position. This means that a row that existed before is not shown any more, and that my edited row now shows up twice. The problem is resolved once I switch to any other view (e.g. the “Account Balance Chart” graph) and back to the transaction view. This is especially annoying when editing multiple transactions at once, as some transactions will not be shown.

I have added screenshots that show the steps to reproduce, namely 1) have at least 2 transactions (in my example two different dates and a Note “first” and “second” for each of them). 2) Edit the date/time so that the order of the two transactions should change (view is set to order by date). 3) After editing the date of the second transaction, this second transaction is now shown twice, and the first transaction disappeared. 4) After switching to another view, everything is correct and both transactions are shown again.

Screenshot 2022-11-20 at 18.47.52
Screenshot 2022-11-20 at 18.48.06
Screenshot 2022-11-20 at 18.48.13
Screenshot 2022-11-20 at 18.56.51

My environment:
Version: 0.59.3 (Nov 2022)
Platform: macosx, x86_64 (OSX Monterey 12.6.1 (21G217))
Java: 11.0.15+10-LTS, Azul Systems, Inc.

Please let me know if you need any other information!


It seems I can’t edit my initial post. It is still happening with the current version (0.61.4 (März 2023))

Version: 0.61.4 (März 2023)
Platform: macosx, x86_64
Java: 17.0.5+8-LTS, Azul Systems, Inc.

Please update your PP to the latest version first.
The current version is the 0.61.04
After that, check if the error still exists.

Attention! Please update to Java version 17 as well!


Thanks for the reply! Sadly, to quote my last post: “It is still happening with the current version (0.61.4 (März 2023))”

I have updated the GitHub issue with my current environment version accordingly :slight_smile: