My apologies - this post should have appeared before my other post at 16:01. NMSS uses offline entry for calendar events to enter ticketed transactions for events (and sometimes donations). Currently, we are forced to enter the batch ID field into the check number field on these transactions because the batch ID field does not exist there. This creates dirty data in our database (because the batch ID is in the wrong place) and creates extra work to close out batches for chapters (we have to run two reports and combine them).
It is not included in the request, but it would also be helpful to have the Batch ID field available on the donation campaign entry page which is accessed through the transactions tab in Constituent360. We use the check number field workaround on this screen as well.
My apologies - this post should have appeared before my other post at 16:01.
NMSS uses offline entry for calendar events to enter ticketed transactions for events (and sometimes donations). Currently, we are forced to enter the batch ID field into the check number field on these transactions because the batch ID field does not exist there. This creates dirty data in our database (because the batch ID is in the wrong place) and creates extra work to close out batches for chapters (we have to run two reports and combine them).
It is not included in the request, but it would also be helpful to have the Batch ID field available on the donation campaign entry page which is accessed through the transactions tab in Constituent360. We use the check number field workaround on this screen as well.