This is not planned - however we have just started an early adopter program for "grid view batch" in webview that will more closely mimic database view batch functionality. Stay tuned on the What's New for the release of this functionality.

One major field that is missing, which the AdvServices staff uses for quicker processing is the Fund ID (and NOT the description). (Much easier to memorize a shorter numeric/alphanumeric fund ID).

Part of functionality is also the processing speed in wv is MUCH slower. Imagine having to explain to your director (who used to do dbv gift processing) all the reasons why it takes SO much longer to process the same number of gifts in WV. The pulsing green dot doesn't even allow you to keep entering info (dbv does - it 'catches up).

linking to a recurring gift, tribute, proper gift subtypes... webview batch is not useful

much easier to navigate large amounts of gifts in a grid form allows for quickly seeing whats missing, copying down a value in a a column. assigning default values, glabally changing values - - using consituent fields to see certain values. Webview batch was never meant for large batches.

Hi Emma!

Can I get some more information on the different parameters that cause different data/workflows to be needed in webview batch? Are there additional fields that need to be added, additional defaults. What fields are you changing in database view that aren't in webview?

Thanks for any additional info you can provide!