In our previous donor database, every gift was processed in a batch. After we closed a batch, another consecutive batch number automatically opened, and accounting compared deposits to batches semi-weekly.
In the Salesforce NPSP Data Import Batch feature, the process seems to work a little differently? I've read the documentation at
https://powerofus.force.com/kA01E000000PZAF, the PDF at https://powerofus.force.com/kA0800000000I8W and watched the demo at https://www.youtube.com/watch?v=afv3DHg5E2kand still only sort of understand the tool.
It looks like the main purposes of the tool are to:
1. Save a configuration on how certain kinds of batches can be processed
2. Enable the scheduling of batch processing
What I haven't been able to do is:
A. Map or import the NPSP Data Import Batch FIELD into the NPSP Data Import object via .csv file using the NPSP Data Import Wizard. It's a lookup field, so I don't know if that makes a difference. I can import the file, then manually add values to the NPSP Data Import Batch field in the NPSP Data Import object after import and before batch processing. But with more than ~5 records, that becomes pretty cumbersome.
B. Receive a batch number or other batch identifier after the batch process is completed.
Perhaps a better workflow is to build reports that positively identify batches by date entered and a secondary field included in each opportunity record. But I'm just wondering if there are any regular batch users that can review the above and see whether I've got my facts straight, or if I'm missing something. We're at the very beginning of our production rollout, so I've still got time to keep all gifts in batches if that's how the org wants to go.
Thanks!
Eric
Yes! Thanks @Melissa Barber. Hopefully it can help others on their journeys.