Recognition credits not added to revenue imported with multiple splits into an Enhanced revenue batch

Within CRM, it is possible to import transactions for constituents with multiple splits.  When the batch template being used has Application defaulted to Donation, if the batch is committed without looking at each transactions' recognition credits in the batch, the revenue will be created without any recognition credits

1.  Remove the Application Default of Donation from your batch template
1.  When editing your batch, click Revenue, Recognitions, and then click OK for each batch row.  
2.  Save your batch.  This will save your recognition credits so that when you commit your transactions they will show up on those records. 

Steps to Duplicate

1.  Log-in to 4.0
2.  Go to Constituents, Batch Entry, Batch Templates, and create an Enhanced revenue batch with the Application field defaulted to Donation. 
4.  Go to Constituents and add a Household of two individuals. 
5.  Create an import template with the following fields:
Date:  todays date
Lookup ID:  Individual from step 4
Constituent:  Individual name from step 4
Designation 1:  2000ANNUAL
Application Type 1:  Donation
Applied 1: $2,000
Designation 2:  2000MEMBER
Application Type 2:  Donation
Applied 2:  $3,000
Amount:  $5000
6.  Go to Administration, Import, and add an import process for the batch template you created in step 2. 
Map your fields
Map the fields that are appended with a 1 and 2 to the Additional Application streams collection field
*  On the Set Options tab under Other:  Mark Quick find under Search list fields
7. Save and start your import process.  
8.  Edit your batch and click Show all messages. Click to Dismiss any errors. 
3.  Update projected totals, Validate, and commit your batch.  
4.  Go to your constituent.  On the Summary tab, go to the donations that were created and notice that neither application has recognition credits applied.    


 Blackbaud CRM
 Service Pack 10

Was this article helpful?

Thanks for your feedback! Did this solve your issue?

Comments (optional):

Thanks for your feedback!
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):
