This is probably the biggest reason we do not process batches in unified view unless we have to. If this were available, if unified view were at parity with database view, we would probably be using unified view batch entry right now.
I always use this feature of generating a static output query as part of committing a gift batch.
It is indispensable for my workflows. I use it for:
review committed batches by other team members for errors/omissions etc
globally make changes to gl/gift dates or appeals or acknowledgment status if the original setting of the batch turned out to be incorrect or incomplete
add information (for ex. gift attribute or gift reference) that was later decided needed to be added to the gifts
unpost gifts in a batch if unposting is needed
These are just a few things that immediately jump to mind.
Yes, I realize that I can build my own gift query using the batch number but that option always opens one up to typo mistakes where the incorrect batch number is entered due to inadvertent transposition of numbers, for ex. and then valuable time and nerves are expanded on trying to figure out what happened and where the gifts one is looking for. Having the option of automatically generating an output query removes this possibility and saves precious time.
I regularly use the option to "create a query" when committing a batch and then use that static query to generate things required by our auditors. Please bring this over to webview!
This function is CRUCIAL to the way we track and save gifts for our finance compliance regulations. It exists in database view when committing a batch via a template and the 'create a query" box is checked. Please add this function back in WebView.
The static output query is essential. Please roll this out, along with the ability to make global changes in NXT batches.
This is necessary for us to generate the reports that we need for our finance team!
This is probably the biggest reason we do not process batches in unified view unless we have to. If this were available, if unified view were at parity with database view, we would probably be using unified view batch entry right now.
I always use this feature of generating a static output query as part of committing a gift batch.
It is indispensable for my workflows. I use it for:
review committed batches by other team members for errors/omissions etc
globally make changes to gl/gift dates or appeals or acknowledgment status if the original setting of the batch turned out to be incorrect or incomplete
add information (for ex. gift attribute or gift reference) that was later decided needed to be added to the gifts
unpost gifts in a batch if unposting is needed
These are just a few things that immediately jump to mind.
Yes, I realize that I can build my own gift query using the batch number but that option always opens one up to typo mistakes where the incorrect batch number is entered due to inadvertent transposition of numbers, for ex. and then valuable time and nerves are expanded on trying to figure out what happened and where the gifts one is looking for. Having the option of automatically generating an output query removes this possibility and saves precious time.
I regularly use the option to "create a query" when committing a batch and then use that static query to generate things required by our auditors. Please bring this over to webview!
This function is CRUCIAL to the way we track and save gifts for our finance compliance regulations. It exists in database view when committing a batch via a template and the 'create a query" box is checked. Please add this function back in WebView.