You are here:
Considerations for Gift Processing Nonprofit
Gift entries that aren't part of a gift batch are processed when you save them. For gift batches, complete a batch dry run and then explicitly process the gift entries in the batch.

Brug mere generelle søgeudtryk.
Vælg færre filtre for at gøre søgningen bredere.
You are here:
Gift entries that aren't part of a gift batch are processed when you save them. For gift batches, complete a batch dry run and then explicitly process the gift entries in the batch.
| REQUIRED EDITIONS |
|---|
| Available in: Lightning Experience |
Available in: Enterprise, Unlimited, and Developer Editions with Nonprofit Cloud |
It's not uncommon to add gifts to batch over a period of time. You might enter some of the gifts today and finish entering them at the end of the week. And in between, the data in Fundraising might change. Tracking these changes manually is cumbersome. To help prevent errors from occurring when you process your batch, initiate a batch dry run.
Batch dry runs simulate batch processing, validating the data and giving you the opportunity to correct errors. However, they don't commit anything in the database or create any records. You can address the errors and then actually process your batch.
For example, the dry run alerts you that the total count of gift entries in the batch doesn't match the estimated count of gift entries. You can review the gift batch and check for any missing entries, or correct the estimated count, or skip this check altogether, and then proceed with the actual processing of the batch.
During a batch dry run, you can't add or edit gift entries. After the dry run is complete, you can add, edit, or process gift entries.
You can process up to 50,000 gift entries at a time in a gift batch. When you process a gift batch, these records are created or updated for each gift entry in the batch:

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.