But when working with long list of found transactions, it's easier to work on a small batch a time - especially when having to scroll through the list checking transactions where you want Replace applied.
After Replace function is applied, the list is refreshed back to the top. User has to scroll down to find where they left off. This can be a painful process when working with a long list. If a custom date range, or even just a start date, can be selected, it's easier to go through a subset of transactions to work with. Example: display defaults earliest to recent. One might choose to do 6 months a time. After the first Replace is applied, change the start date to 6 months later so the start of the list is, once again, only transactions you need look at - not the entire list again and again.
