Gender defaults to unknown when importing new constituents in the Constituent Update Batch

When importing new constituents via the Constituent update batch the gender defaults to unknown instead of the gender of the constituent on the row that is being imported.
Download and install the latest patch which contains all fixes from previous patches. If you are running an older version, download and install the latest version and then the patch.

Steps to Duplicate

Steps to duplicate:

 

Test 1 (without lookup ID)

1. Create a CSV file with columns with these header names: Constituent, Constituent Type, first name, last name, gender.

2. Fill in data in the CSV file for an existing constituent, leave the gender field blank.

3. For the Constituent Update batch template, leave the Gender field blank instead of the default value of unknown.

4. Create an import process based off of the Constituent Update Batch, and map the fields in the import to the csv file

4. Run the import process to create a batch

5. Go to batch entry and open batch, notice that the gender field defaults to unknown


Test 2 (with LookupID, I used same CSV file and just edited it)

1. Create a CSV file with columns with these header names: Constituent, lookup ID, Constituent Type, first name, last name, gender.

2. Fill in data in the CSV file for an existing constituent, leave the gender field blank.

3. For the Constituent Update batch template, leave the Gender field blank instead of the default value of unknown.

4. Create an import process based off of the Constituent Update Batch, and map the fields in the import to the csv file

4. Run the import process to create a batch

5. Go to batch entry and open batch, notice that the gender field defaults to whatever is already on the constituent's record, you are not able to update this field. If the gender field is marked as unknown on the constituent's record and the customer would like to change it, they cannot do it through import\batch unless they specifically enter in a gender on the csv file.

 

Environment

 Blackbaud CRM
 3.0
 4.0
 Service Pack 5

Was this article helpful?