Validate addresses (all rows) task does not validate addresses when importing constituent information into an Enhanced Revenue Batch

With address standardization turned off and constituent updates set to ignore similar addresses, you might notice that street abbreviations will not change to the desired format when the Validate addresses (all rows) task is used when importing an ERB. However, opening the Edit Constituent task in the batch and clicking the Validate button on that form will result in the desired address format.
We are currently evaluating this issue for a fix in a future service pack. 

Steps to Duplicate

1) Create a constituent and add an address with the street suffix spelled out. (ie: 84 Main Street).
2) Create another constituent with an address that has a direction. (ie: 62 West Palm Rd.)
3) In Administration > Global Data Entry Settings > Turn off Address Standardization. In the Constituent Updates section, have Addressupdates for similar and dissimilar addresses be ignored.
4) Import revenue for these constituents using an Enhanced Revenue Batch.
5) Using the New/Edit Constituent Collection field, map the address information for these two new constituents.
6) For the constituent created in step 1, abbreviate the street suffix (ie: 84 Main St.)
7) For the constituent created in step 2, abbreviate the direction (ie: 62 W Palm Rd.)
8) Import the batch.
9) Go to the newly created batch and click Validate addresses (all rows).
10) Open the Edit Constituent window and notice that the address box contains the value from the import file.
11) Click the validate button in the Edit Constituent form and notice that the value changes to the desired address format.
 

Environment

 Blackbaud CRM
 4.0
 4.0.173.0

Was this article helpful?