Credit card batch template is incompatible with rejection handling after upgrade to 3.0.

Problem: When using an existing batch that contains custom fields from a batch extension for credit card processing process, users receive the error: This batch uses a template that is incompatible with rejection handling behavior.  No special action will be taken on rejected transactions.

This is a generic error message warning the user of a discrepancy in the batch template. 

When upgrading to CRM 3.0 new, hidden, fields are added to batch templates to aid in rejection handling. Batches which were created in a previous version of CRM will not be updated and therefore do not have these fields.

The solution is to delete and then recreate the batch in the 3.0 environment. The user does not need to make any changes to the batch template.




Was this article helpful?