I just created a rule to set the category for a given payee. AFAIK did not request that it change the category on existing transactions, but dicovered that they all had been changed … 40+ transactions over 3 years. And Per tech support there is no way to undo this. Since this is a payee that goes in multiple categories, I have no good way of manually undoing this action. Two different features could prevent this problem for myself and others in the future
twellspring is dead on. This is a TERRIBLE UX problem right now — the option to apply a category change to hundreds of transactions is way too subtle and way too easy to accidentally do…. and the undo prompt is way too subtle and way too shortlived to be useful. My wife just accidentally reset categories on over a thousand Amazon transactions… my soul has died inside thinking about how much work it will be to fix… WHY OH WHY WOULD SIMPLIFI MAKE THIS SO EASY TO DO?!? TERRIBLE!
I agree with the need for an undo button. Or a restore point capability, such as restoring to the previous day (this would be a simpler resolution approach if someone truly screwed up their transactions).
An undo option MUST be added as well as a warning: “Are you sure you wish to recategorize ALL past entires with this category?” Had that been there, I would have clicked NO.
Just like the others, I lost 2 years worth of Amazon transaction categories. I'm a new user and this could be a deal breaker if you don't provide an option to go back to previous data. It took days to categorize those transactions and one checkbox wiped it out! The toast for "undo" is way too fast.
@kab , I feel for ya. This just happened to me for the first time the other day. 2 year’s worth of transactions - for one payee - recategorized in .05 seconds. Fortunately, mine will be easier to undo than yours. Don’t give up!
I have just decided to stop using Simplifi over this very issue. Hours and hours of work to categorize transactions gone in an instant with no way to undo it. No one should ever use this software while this problem still exists.
This idea was proposed in 2021. Did it ever see the light of day? If ideas are not being developed maybe the dev team could provide some feedback as to why. Seems as I read these posts a lot of new users from mint and ynab joining Simplifi. Could we at least understand how these ideas are prioritized after votes are cast?
@Coach Natalie
The "Undo" option only allows users to step back an instant, and human error would suggest your team could devise a way to have errors/mistakes removed back to the origin by clicking the "back" arrow, like other programs (Excel, Word, etc.)
An "Undo" button doesn't seem to be on the horizon.
So here a couple of other approaches, specific to the "accidental recategorization" problem, that might help:
(1) Have QS to show a popup window listing the transactions that will be affected, with the choice to Cancel or Continue. (Conceptually, this is similar to the way creating a recurring transaction works. QS shows you a list of the upcoming reminders so you can look at it and see if it looks like what you really wanted.)
(2) Less difficult would be for QS to pop up a warning window saying "This rule will modify XXX transactions. Cancel or Continue." That would at least give the user the opportunity to realize the magnitude of the change and perhaps rethink it.
Yes, I upvoted this as well as the idea to have a backup and restore capability. The votes on both of these are pretty low, so I don't see it happening.
However, I agree with @DryHeat that a MAJOR warning should be given to users unaware of the magnitude of some of their changes.
I agree with this. Warnings should be given when a user is about to change a lot of data at once.