All gift batches created in database view should be in NXT
Before sun setting database view, all gift batches should at least be viewable in NXT. Ideally, we should also be able to continue committing recurring batches that were created in database view and not lose the history or data from those batches.
In an effort to use wv, I keep trying to open dbv batches in wv - to review & make corrections before a batch is committed or research after it is committed. Yes, even after a batch is committed, we will call them up when our Finance team has questions and need to research procedural questions (eg, does the template need to be updated, what defaults did the processor use, etc.)
We have held out going to wv until more of our needed batching functionality was available - mainly because my gift processors did not have the bandwidth to go into dbv to keep fixing things like tributes, etc. during our super high-volume months of September and October. (Muscle memory is especially crucial during this time - constant changes/upgrades to a screen can be detrimental to error-free processing).
They are looking forward to learning the new wv batching, but not while it adds work that is ongoing or constantly changing - and is not just training time (which is assumed to be temporary).
We store a lot of batch data, like the ticket number for the batch, in the batch descriptions and we regularly go look at old batches for various reasons. I kind of assumed this would all roll over into NXT, since the NXT batches all show up in DB, but I'm voting for this in case it wasn't planned. We cannot lose access to that historical data. Aside from my need for it, my finance team would kill me if I couldn't look that stuff up for them anymore.
I agree we need to be able to see all DB view batches in web view for reference.
We have gift batches in DB view organized and saved in folders by year. The ability to organize them in web view by user preferences is a must. It would be ideal if DB view batch folders are moved to web view.
In DB view batch, we use a general folder for creating new batches. The batch stays there until acknowledgement letters are generated. Once they are done, the batch is move to the year folder. We also have batch folders for batch templates and web view batches. The web view batches are moved to the year folder once they appear there after being approved in web view.
In an effort to use wv, I keep trying to open dbv batches in wv - to review & make corrections before a batch is committed or research after it is committed. Yes, even after a batch is committed, we will call them up when our Finance team has questions and need to research procedural questions (eg, does the template need to be updated, what defaults did the processor use, etc.)
We have held out going to wv until more of our needed batching functionality was available - mainly because my gift processors did not have the bandwidth to go into dbv to keep fixing things like tributes, etc. during our super high-volume months of September and October. (Muscle memory is especially crucial during this time - constant changes/upgrades to a screen can be detrimental to error-free processing).
They are looking forward to learning the new wv batching, but not while it adds work that is ongoing or constantly changing - and is not just training time (which is assumed to be temporary).
We store a lot of batch data, like the ticket number for the batch, in the batch descriptions and we regularly go look at old batches for various reasons. I kind of assumed this would all roll over into NXT, since the NXT batches all show up in DB, but I'm voting for this in case it wasn't planned. We cannot lose access to that historical data. Aside from my need for it, my finance team would kill me if I couldn't look that stuff up for them anymore.
I agree we need to be able to see all DB view batches in web view for reference.
We have gift batches in DB view organized and saved in folders by year. The ability to organize them in web view by user preferences is a must. It would be ideal if DB view batch folders are moved to web view.
In DB view batch, we use a general folder for creating new batches. The batch stays there until acknowledgement letters are generated. Once they are done, the batch is move to the year folder. We also have batch folders for batch templates and web view batches. The web view batches are moved to the year folder once they appear there after being approved in web view.