I am using the API to create a gift batch, add gifts and then close the batch using something similar to the sample code in the API documentation. In testing against the Sample Database, this works as expected, with additional Campaign, Fund and Appeals being populated as well. However, once we used it against the production database, the Campaign, Fund and Appeal codes come up "null" in the database, even though we have verified those items exist in the database. What is interesting is that the appropriate Campaign, Fund and Appeal codes are available for selection when going through Data Entry on the Gifts, so I am wondering if there is some additional validation we need to do when getting these items linked up for each gift.

Does anyone know if there is any additional documentation on differences in validation between API created Gifts and Gifts added through the Raiser's Edge client?

 

You might check User Options --> Records for the current RE user and see if they are set to use Description if you are using the long description for the C/F/A's, or "ID" if you are specifying the ID in your import file instead of the description. If, for instance, the user option for appeal is "Description" and your data file contains the Appeal ID, RE will not be able to match to that appeal and the batch field will be null.