Editing transactions inline on the web app is not saving changes until clicking elsewhere (edited)
Hi team,
I noticed starting in mid February, around the time some of the custom report features were rolled out, making an inline edit to a row on the transactions page does not result in a server request to persist the change. Specifically, the PUT to the services.quicken.com/transactions/{transaction_id} doesn't fire until you click somewhere else on the page.
So for example, if I click the "Reviewed" checkbox on an un-reviewed row, it will update the page state (i.e. it will add the green checkmark), but it won't actually send a request to the back end to save that change. As soon as I click anywhere else on the page, the xhr request will go thru and I'll get a toast popup that the transaction was updated.
This isn't just impacting the "Reviewed" checkbox; it's impacting all inline edits. For instance, if I change the transaction category from the inline dropdown, the server request won't go thru unless/until I click on something else on the page.
As a result, the current workflow looks something like this:
- Update transaction 1. (nothing happens)
- Update transaction 2. (the browser sends a PUT to update transaction 1. I get a success toast message)
- Update transaction 3. (the browser sends a PUT to update transaction 2. I get a success toast message)
- Click somewhere else on the page. (the browser sends a PUT to update transaction 3. I get a success toast message).
The workaround above (i.e. step 4) isn't terribly difficult, but it'd be awesome if you could address whatever is preventing these updates from being fired on the initial change.
Thanks,
Mike
Comments
-
Yup, I've been experiencing the same. It's a bit annoying and I hope it'll get fixed!
0 -
Reposting with more details from another thread:
A very real issue is that simply clicking Reviewed, or changing a category or anything inline doesn't force the transaction to save immediately - the save only happens when you make the next mouse click (or probably when pressing tab iirc). Therefore, if you edit a transaction so that it no longer meets the filter criteria that you're using right now on the transaction list, it won't disappear until the next click. This is very easy to replicate using the steps in OP - filter the transaction list by Reviewed = TRUE, click the Reviewed checkmark to review any transaction, and watch. It won't go away until the next mouse click (which might be clicking Reviewed on another transaction, or not). The same thing happens if you filter on a category and change a category so that it no longer meets criteria.
Another way to replicate this issue is to categorize a transaction as a Transfer to a manual account (or to an account where the matching transfer transaction doesn't exist yet). Simplifi will pop up a little question asking if it should create the other side of the transfer manually, but not until the next click. If your next click is on a different transaction then you get a nice little interruption and have to remember which transaction you were thinking about before.
I've been dealing with this issue for a few months and it's quite annoying (though I am getting somewhat used to it which helps). I am pretty sure it started with the New Register / New Transaction List. I hope it can be fixed!
[corrected formatting]
0 -
Hello @EL1234 and @simplify_mn,
I was able to reproduce this issue as well and have reported it to our product team. We will be sure to follow up here with any updates as they work toward a resolution!
Thank you!
SIMPL-33048
-Coach Jon
0 -
Thank you @Coach Jon
0
