Abatement Entry goes back to record 1 of X after an update

Abatement Entry reverts to first record in the batch after updating a subsequent record.

• Munis 2019.1 and up

• Abatement Entry

• txabtent

Development is currently researching the issue. After updating an abatement in the batch, the navigation buttons at the bottom of the screen or the browse option in the ribbon menu can be used to return to the desired record.

In addition to reverting back to the first record in the set, the customer information that is shown onscreen may also display as an artifact from the prior record that was updated. This is simply a display issue and not indicative of a data problem. Refreshing the screen by navigating to the Next record and back will cause the proper customer information to display on the abatement as will redoing a find or selecting from the browse list.