I apologize if this has been asked before, I have searched but missed finding. If there is existing info please let me know.
What is the best way to review what will be added/updated by the synchonize command to merge a database into the open one, before it is done? Or after it is done?
Sometimes there are things synchronized (from Keepass point of view it is correct) but may not be wanted. Mostly I try to keep notes about what that might be so I can fix manually after, but sometimes I have not and an audit log of changes would help me figure out what those are.
Has anyone had a need to do this, and what did they do? I did try various export formats at some point (it was quite some time ago), IIRC there were a lot of KeePass-centric differences included that made it really difficult to isolate user changes.
TIA for any help and ideas.
Kind regards.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks Paul. Yes I'm aware of the History, but didn't even think to check the menus for reports like Find -> Last modified entries. D'oh! Thank you. That helps me narrow down what was changed so I can go review from there. I would love having a sync report of the actual fields changed but I realize that my use case is probably not common enough to warrant creating that if it doesn't already exist. I'll work with this and go from there.
It's complicated. Several people share a database and it's user error for sure. Sometimes a person intends to make changes and updates the database, but then for whatever reason those changes don't happen or don't commit and the person has forgotten to revert their changes. Sometimes they're not even sure which entries were compromised. So Keepass faithfully syncs the most recent change as the latest data. Up until now I have relied on person having some idea and/or comparing before/after dumps of the database. This report (again TY for pointing out the obvious!!!) should cut down my efforts considerably.
Last edit: appyface 2026-03-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I apologize if this has been asked before, I have searched but missed finding. If there is existing info please let me know.
What is the best way to review what will be added/updated by the synchonize command to merge a database into the open one, before it is done? Or after it is done?
Sometimes there are things synchronized (from Keepass point of view it is correct) but may not be wanted. Mostly I try to keep notes about what that might be so I can fix manually after, but sometimes I have not and an audit log of changes would help me figure out what those are.
Has anyone had a need to do this, and what did they do? I did try various export formats at some point (it was quite some time ago), IIRC there were a lot of KeePass-centric differences included that made it really difficult to isolate user changes.
TIA for any help and ideas.
Kind regards.
There is no way to know what will be changed, but it doesn't matter because all data is saved in the History so nothing is lost.
To see what changed, select Find > Last Modified Entries.
FWIW, I have never needed to find old data after a sync, only after an edit and once you fix that the sync will have the same data.
cheers, Paul
Thanks Paul. Yes I'm aware of the History, but didn't even think to check the menus for reports like Find -> Last modified entries. D'oh! Thank you. That helps me narrow down what was changed so I can go review from there. I would love having a sync report of the actual fields changed but I realize that my use case is probably not common enough to warrant creating that if it doesn't already exist. I'll work with this and go from there.
It's complicated. Several people share a database and it's user error for sure. Sometimes a person intends to make changes and updates the database, but then for whatever reason those changes don't happen or don't commit and the person has forgotten to revert their changes. Sometimes they're not even sure which entries were compromised. So Keepass faithfully syncs the most recent change as the latest data. Up until now I have relied on person having some idea and/or comparing before/after dumps of the database. This report (again TY for pointing out the obvious!!!) should cut down my efforts considerably.
Last edit: appyface 2026-03-02