making bulk memo corrections more efficient
I make insurance premiums twice monthly to the same homeowners' insurance company. Each premium is for a different policy.
In the past I would simply fill in the memo field for each payment "house, car, boat, umbrella". I recently decided to better define the payments. One payment "car, boat, umbrella" and the other "house".
I do a search on the payee's name and all payments show up. I go to modify one memo and then I have to go back to doing another search in order to correct the next memo.
It would be quicker and more efficient if the search results would "freeze" so I could see and correct all memo fields. Find & Replace doesn't do it well nor does it take into account typos.
For example, if my Search results in 50 transactions that I want to change, all 50 transactions would stay visible until I decide I'm finished. The current method is to do 50 separate searches. Time-consuming as well as wasteful.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by Stuart Beesley ... on 06 Sep, 2023 12:13 PM
Try the Find and Replace extension?
2 Posted by Charles McEniry on 06 Sep, 2023 01:07 PM
I looked at Find/Replace but not the easiest to do with what I wish to
accomplish.
It still does not deal with typos. All memos are not written the same.
Something as simple as an added space or comma would throw off the search.
It would be far better to be able to search and then freeze those
results so that ALL relevant memo fields could be edited. Once editing
is finished, then the items would unfreeze. Right now I have to edit
each memo field individually. I edit and save one field only to have
the transactions return to normal display. I have to do another search,
edit the next field, save and it again displays the transaction list.
On 9/6/23 07:13, Stuart Beesley (Mr Toolbox) wrote:
System closed this discussion on 06 Dec, 2023 01:10 PM.