Constituency (Stored-value) missing constituencies after merge

After merging two constituent records (one with the Constituency and one without) and running the Constituency Stored-Value Refresh process, the CONSTITUENCYDATERANGE does not reflect the appropriate Constituentid even though the Constituency shows accurately on the Target Constituent Record.
We’re currently evaluating this issue for a fix in a future release.

Steps to Duplicate

  1. Created and added a User-defined Constituency with a DateFrom and DateTo entry to a Constituent Record
  2. Run the Constituency stored-values refresh process without a selection used:

User-added image

  1. Check to see if it is on the CONSTITUENCYDATERANGE table
  2. Edit the constituency DateFrom and DateTo entries on the Constituent Record (Personal Info > Constituencies tab)
  3. Run the Constituency stored-values refresh process without a selection used
  4. Check to see if it changes on the CONSTITUENCYDATERANGE table as expected (yes)
  5. Merge the constituent containing the constituency with another constituent that does not have the same user-defined constituency (Constituent > Duplicates > Merge two constituents process):

User-added image

  1. Run the Constituency stored-values refresh process without a selection used
  2. Check to see if it is on the CONSTITUENCYDATERANGE table with new constituentid (no)
  3. Check to see if it is on the CONSTITUENCYDATERANGE table with the old constituenitd (yes)
  4. Review the Constituency details on the Target record from the merge and note that the Constituency is showing accurately:

User-added image

Environment

 Blackbaud CRM
 4.0
 6

Was this article helpful?