Query pulls old model scores and changes date of records in results

When Attribute categories set up for a specific ministry and imports in new model scores and ratings and then a query is used with the most recent start date for the attribute categories it is found that the query pulls the old attribute categories and changes the start date to the start date that was declared in the query.
We’re currently evaluating this issue for a fix in a future service pack.

Steps to Duplicate

  1. Click Constituents/Constituent search
  2. Search for constituent and click Wealth and ratings under More information of the left hand side of the page
  3. Click Model Scores and notice that the constituent has GM - Lapsed Cluster, GM- Lapsed Score, and GM-Lapsed Tier twice. The first three were updated for example on 3/17/2016 and the second three were updated for example on 9/29/2016 and both sets have different Scores
  4. Click Analysis\ Information Library\ Add Ad-hoc query\Constituent
  5. Click Model Scores and Ratings and expand the Attributes folder
  6. Map the Following fields to include: LookupID is equal to the constituent that you searched for, and Model Scores and Ratings\GM-Lapsed Tier Attribute\Value is not blank, and Model Scores and Ratings\GM-Lapsed Tier Attribute\Start date is 9/29/2016
  7. Add the following fields to the Results fields to display: Name, Model Scores and Ratings/GM-Lapsed Score Attribute/Value, Model Scores and Ratings/GM-Lapsed Tier Attribute/Value, Model Scores and Ratings/GM-Lapsed Tier Attribute/Start date
  8. Click Preview results and notice that is pulls the old attributes and gives it the date 9/29/2016 and also changes the rest of the fields to a mix of the new and old scores in the results.

Environment

 Blackbaud CRM
 4.0
 4.0166.0

Was this article helpful?