I've got a DLRS that appears to be regressing. There are 127 records that I had manually edited and saved to trigger an update earlier in the week (Wednesday, I believe), and today all of those records somehow reverted to the previous value. I turned field tracking on and so was able to spot check several, and I see the rollback changes all seem to have happened at 2AM. This process is looking at the last advancement visit date (i.e. the most recent task with a Category = "Meeting" and a Status = "Completed").
My knowledge of DLRS is pretty shallow, but here are the specs I'm using:
Lookup Relationship
Parent Object: Account
Child Object: Task
Relationship Field: WhatId
Relationship Criteria: Type = 'Meeting' AND Status = 'Completed'
Relationship Criteria Fields: Type, Status
Rollup Details
Field to Aggregate: ActivityDate
Active: Y
Field to Order By:
Calculation Mode: Realtime
Aggregate Operation: Last
Calculation Sharing Mode: System
Aggregate Result Field: BMG_Acct_Last_Advancement_Visit_Date__c
Aggregate All Rows: Y
Row Limit:
Text Lookups
Concatenate Delimiter:
Description
Description:
Advanced
Test Code:
Test Code See All Data: N
Can anyone help me figure out why my result field is reverting back to older outdated task dates rather than referencing the most recent date as I intended?
#Data Management #DLRS Field @Commons Project: DLRS @Data Quality & Management
Hi @Aaron Yost, looking at the definition you outlined, it doesn't look like you have a value in "Field to Order By". If you want to return a value from the "Last" record, ie, the most recent, you have to tell DLRS to order by ActivityDate.
