When a gift batch is approved (committed), the Grid View should retain a complete, read-only snapshot of the batch exactly as it was entered at the time of processing. While users may later edit gifts in Raiser's Edge NXT, the original batch should continue to display the original values and field entries for audit, validation, and troubleshooting purposes.
This would align more closely with Database View behavior, where users can reopen a committed batch and see the original data as it was entered, even if subsequent changes have been made to the gift records.
This slows down gift entry and batch approval in NXT. Yesterday I reviewed a batch, writing a list of gifts for the entry person to correct. I backed out of the batch, and when I came back in to continue review and list corrections the gift order was scrambled. I hate to think of the lag time my team will encounter during year end high volume.
Agreed! This is super aggravating to deal with! Our org often enters a batch and saves it for further information before approval, and reviewing it in some other order is ridiculous.
I think being able to keep gifts in the order entered is essential! It would also nice to be able to sort by other columns, but be able to revert back to the "how they were initially entered" order.
This is essential for our gift entry and review/commit process. Gifts are entered from scanned checks/documents in a specific order. Review and commit the same.
This is a serious flaw in regards to proofing and auditing purposes. Please program a way to keep (and return to if a sort is created) the original gift entry order.
This is very necessary. Users doing gift entry often have check logs, scans, and/or physical paperwork that is in a specific order and need to be able to match that to the batch when reviewing it.
This is very important for gift batch validation and review. It makes find errors prior to approval extremely challenging. At times it can even be challenging to reconcile with FE.
This is very important for our process. We currently use Mail to export a file to merge for acknowledgement letters and in database view that file will stay in the order gifts are entered. Entering gifts in the new NXT batch changes the order of the gifts and we then had more difficulty matching up each check/documentation with the acknowledgement letter to scan for our records.
This would have been nice to know up front, before we started testing the batches in NXT. I often need to come back to batches as we add checks over multiple days. The order is necessary to keep track of what has been entered and what has been reviewed. Now, I need to delete the whole batch and start over again because everything is out of place. If I had known this was going to be an issue our process would have been needed to be changed.
When a gift batch is approved (committed), the Grid View should retain a complete, read-only snapshot of the batch exactly as it was entered at the time of processing. While users may later edit gifts in Raiser's Edge NXT, the original batch should continue to display the original values and field entries for audit, validation, and troubleshooting purposes.
This would align more closely with Database View behavior, where users can reopen a committed batch and see the original data as it was entered, even if subsequent changes have been made to the gift records.
During entry,when saved, the order is scambled. This make it very difficult to keep from missing a gift, since there is no Sort feature in Batch Grid.
Agree!
This slows down gift entry and batch approval in NXT. Yesterday I reviewed a batch, writing a list of gifts for the entry person to correct. I backed out of the batch, and when I came back in to continue review and list corrections the gift order was scrambled. I hate to think of the lag time my team will encounter during year end high volume.
Agreed! This is super aggravating to deal with! Our org often enters a batch and saves it for further information before approval, and reviewing it in some other order is ridiculous.
This!!! Yes, please!!!
The gifts need to stay in entry order, otherwise it is nearly impossible to double-check data entry.
This is extremely important. In DBV, The gifts are in order, then we can choose to sort them as well. Extremely helpful when reviewing gifts.
I think being able to keep gifts in the order entered is essential! It would also nice to be able to sort by other columns, but be able to revert back to the "how they were initially entered" order.
This is essential for our gift entry and review/commit process. Gifts are entered from scanned checks/documents in a specific order. Review and commit the same.
Additionally, it’d be super helpful to be able to copy the row or the cell directly above.
This is a serious flaw in regards to proofing and auditing purposes. Please program a way to keep (and return to if a sort is created) the original gift entry order.
This is very important for gift batch validation and process. We compare our digital check deposits in the order it is entered in a gift batch.
Should not change order and should have a sort option
This is very necessary. Users doing gift entry often have check logs, scans, and/or physical paperwork that is in a specific order and need to be able to match that to the batch when reviewing it.
This is crucial to my organization for gift batch review and ack production
This is essential for both proofing entry for errors and reporting.
This is very important for gift batch validation and review. It makes find errors prior to approval extremely challenging. At times it can even be challenging to reconcile with FE.
This is very important for our process. We currently use Mail to export a file to merge for acknowledgement letters and in database view that file will stay in the order gifts are entered. Entering gifts in the new NXT batch changes the order of the gifts and we then had more difficulty matching up each check/documentation with the acknowledgement letter to scan for our records.
This would have been nice to know up front, before we started testing the batches in NXT. I often need to come back to batches as we add checks over multiple days. The order is necessary to keep track of what has been entered and what has been reviewed. Now, I need to delete the whole batch and start over again because everything is out of place. If I had known this was going to be an issue our process would have been needed to be changed.