English is not my first language, so I may not have explained the issue clearly before. I have now attached screenshots to illustrate it better. "Google (t...)" is the original entry, which was last modified on 2026-05-26. "Google (a...)" is the duplicated entry. In KeePass history, it appears as if it was modified on 2026-05-26, but that timestamp is incorrect, since I duplicated the entry only a few days ago. If you look at the duplicated entry's own history, you can see that I actually created...
This is particularly problematic when reviewing the global history. Recently duplicated entries may not appear among the newest entries because they inherit an old creation timestamp from the original entry. If the original entry was created or last modified months or even years ago, the duplicated entry can appear far back in the history even though it was actually created recently. As a result, the global history becomes unreliable for identifying entries that were created recently.
Duplicated entry inherits an incorrect creation time
Tysm! I tested it with all the XML replacements I wanted to apply, including renaming custom fields and modifying their values, and I couldn't reproduce the bug. It's working flawlessly now!
Thank you so much! By the way, any update on this? https://sourceforge.net/p/keepass/feature-requests/2990/
I got a working example. Attached database has empty master key (if you wish you can also create the database yourself, as it is default database). In "Sample Entry" add "Test" field with this value (multiple lines): ¿ 0 In "Sample Entry #2" add "Test" field with this value (multiple lines): ? a Don't save the database. Perform XML Replace: Select nodes: //Entry/String[starts-with(Key,'Test')]/Value Action: Replace data Data: Inner text Find what: androidapp://org.mozilla.firefox_beta Replace with:...
XML Replace crashes when "Find what" and "Replace what" are empty
Also, it's for KeePass 2.x, not 1.x. I can't edit my post, but the modified entries indicate "..." (three dots) in the Modified column instead of ".." (two dots). Use the screenshot as the source of truth