jamessimone
Inconsistent Sum Behaviour On CMDT Grandparent Full Recalculate rollup
Hi,
I've noticed some inconsistent behaviour regarding the Grandparent rollup when using the Full Recalculate button or when an update is triggered by a batch job. The rollup to the parent works fine but the grandparent will sometimes double or half the value that should be there. Interestingly, re-running the recalculate will often resolve the incorrect amounts (but sometimes cause other records to become incorrect).
For context in the loom/screenshots: Revenue_Booked__c records are created by a batch job which then triggers two rollups defined by two CMDT to two records, a parent (Credit_Line__c) & a grandparent (Loan__c). This behaviour can also be intermittently observed on using the full batch recalculate via the "Recalculate Rollup" page. I've checked and all objects have the rollup trigger setup correctly (otherwise nothing would work I imagine).
Loom Explainer here
Details about the two CMDT records in question:
- Revenue_Booked__c -> Credit_Line__c (Parent)
- Revenue_Booked__c -> Loan__c (Grandparent)
I've also got Nebula Logger installed in my test org, but can't make heads or tails of what the cause may be & I can regularly replicate the issue.
Version number: 1.6.32
Let me know if any more detail is required. Also fully recognise that it could be something to do with how my rollups are set up. 😄
EDIT: I've been trying to do my own debugging and playing around with batch sizes. I've noted that changing the batch chunk size causes the issue to amplify/exacerbate wildly.
Batch Settings
Cross-Check Report results (over 50% of records are now affected)
Hello, and thanks for submitting this! I will take a look, but I won't be able to begin investigating till next week. Just wanted to keep you informed as to the timeline; I'll follow up here next week with questions.
No worries, thanks @jamessimone, completely understand. And thanks for all your hard work on this!
@jaredcloudyknights apologies for the delay in response - I've finally had the chance to start looking into this issue and thanks to the wonderful video you recorded and the details you've shared here, I believe I've pinpointed the problem. I'm going to do my best to get the fix out with the next version, which I hope to release today
@jaredcloudyknights if you're able to test on the new version, let me know! I made some changes that may help.
@jamessimone sorry just had a chance to update the package and retest. Unfortunately, it looks to still be occurring. I've recorded another Loom here stepping through the reproduction of the issue.
Not to worry. I am continuing to look into this - apologies that it's been slow going
It's my belief that this issue and #615 are related, and I'm continuing to work on a resolution for both