When using a user-defined Enhanced Revenue Batch template for import, one may encounter the following error when no spouse data exists in the import file:
Constituent entered has an existing spouse that is different than the spouse entered in the row.
We are currently evaluating this issue for a fix in a future service pack.
Steps to Duplicate
1. Create an Import process with the batch template in question. Use an import file that contains no spouse data. 2. On the Map fields tab of the Import process window, click Auto-map. Find the New/edit constituent field, highlight it, and click Map collection field. In the Map collection field window, click Auto-map. Click OK. Click Save. 3. Click Start process. 4. In the resulting batch, click Validate. Sometimes the error is thrown at this point. If not, save and commit the batch. The error is sometimes thrown when attempting to commit.