dbo.CONSTITUENT SSNINDEX column is not populated

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'

Environment

 Blackbaud CRM
 4.0

Was this article helpful?


Thanks for your feedback! Did this solve your issue?

Comments (optional):


Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):


Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.