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
