After saving a social security number on a constituent record, a user may notice that the dbo.CONSTITUENT SSNINDEX column is not populated and instead has a value of 'Null'.
We're currently evaluating this issue for a fix in a future patch or service pack.
Steps to Duplicate
1. Log-in to 4.0 2. Search for any constituent record. Note the 'LookupID'. 3. Go to the Personal Info tab>Personal Sub Tab. 4. Under Social Security Number click Edit. Add Social Security number 123456789 and Save. 5. Run the following SQL against the database and see this valu is NULL
SELECT SSNINDEX FROM dbo.CONSTITUENT WHERE LOOKUPID = 'LookupID from step 2'