Rollups not calculating automatically, but Recalc works

[steph-EV]

I've confirmed that the custom setting Rollup Settings has Is Enabled = true. My rollups are configured using the CMDT-driven invocable action in flows. All the flows are triggered when "A record is created or updated", and I used the UPSERT context in the action.

They calculate correctly when I use Recalculate Rollup. However, they don't automatically update on record creation or update. Any help would be appreciated!

[jamessimone]

@steph-EV in addition to the CMDT driven invocable, do you have the Process Deferred Rollups invocable action? Or you can set the Defer Processing? variable in your CMDT-driven invocable to the global constant for false. Let me know if that works!

[steph-EV]

Yes, I have also set Defer Processing to true, and use the Process Deferred Rollup action.

[jamessimone]

Do you have any entry criteria to your flow that would be preventing records from making it further? Thank you for checking over those details for me. Without seeing a log (where Is Rollup Logging Enabled? is set to true on the Rollup Control org default record) it may be difficult to diagnose without further details. We will get this working for you!

[steph-EV]

@jamessimone Thanks for your response!

I confirm that "Is Rollup Logging Enabled?" is set to true on the Rollup Control. And actually, this solved my problem...I was able to see that the one rollup I was not running from Recalc (because it had an error) was causing the problem when doing a record update. So silly of me! I deleted that CMDT and it runs as expected now. Thanks again for your help.

[jamessimone]

No problem! I am really glad to hear — the logging can provide exceptional details that might otherwise be hidden and it makes me happy to know it has the potential for self-service problem finding too! Let me know if there’s anything else you need.

[steph-EV]

Hi @jamessimone

I have the same issue (and setup), but this time it is not due to a malfunctioning rollup.

I have two CMDT records on the same child object. One is a LAST operation, and the other is a COUNT. They both has the same WHERE clause on RecordType.DeveloperName

Both rollups work when I use the Recalculate button. However, only the LAST cmdt calculates when run from a record update / flow. The COUNT does not update in this case. What could be the cause of this? Thanks!

[jamessimone]

Have you looked at any of the logs? Without seeing them, it will be exceptionally hard to address. I would ensure the casing is the same for the where clauses and that there isn't any other automation acting on the field with the count that could be colliding with this

[steph-EV]

Hi @jamessimone , thanks for your reply. What should i be looking for in debug logs? See attached
apex-07LEm0000013mynMAA (1).log
apex-07LEm0000013mvcMAA.log
apex-07LEm0000013kk7MAA.log

I also noticed that the rollups don't recalc on an undelete. Is there something I need to do specifically for that? thank you!

[jamessimone]

There aren't any rollup-specific logs in what you've attached. That's OK though. For your info, COUNT based rollups behave a bit differently from what you might expect, and I think this is probably the reason for the confusion:

• in a full recalc, the current values for all rollup fields are recalculated
• in a count operation, if a record is updated, Apex Rollup first checks if the rollup field on a given child record has been updated. If it has not been updated (which is frequently the case), it does not update the parent record because that record has already been counted. The exceptions to this rule are as follows:
  • if the child record's lookup field has changed to a new parent
  • if fields in the SOQL where clause have updated such that the old version of the item was not a match, and the new version of the item is (or vice versa; this would decrement the parent field).

Undelete should "just work" but it requires the use of an Apex Trigger - Flow does not support UNDELETE for record-triggered flows, and I believe you're using Flow to invoke Apex Rollup.

[steph-EV]

Hi James,

I didn't understand about COUNT...what is the best practice for implementing it?

[jamessimone]

@steph-EV all of that is to say that COUNT works by inserting/deleting new children. Updates to existing children shouldn't increment a count-based rollup. you can force a COUNT rollup to always recalculate by toggling the Is Full Record Set checkbox on the associated Rollup CMDT.

If you need to support undelete operations, undelete is not supported by Flow - you would, at bare minimum, need an Apex trigger with the after undelete context defined that called Rollup.runFromTrigger();

[hgughane]

Even i am facing same issue, I do check Rollup Settings has Is Enabled = true, can somebody help me if i missed some setting.

Calling Rollup.runFromTrigger(); from trigger, below is the screenshot for same.

It's calculate correctly when I try via Recalculate Rollup, but same thing when i tried from trigger, calculation is not calculating properly.

[jamessimone]

@hgughane when you say “calculation is not calculating correctly” - what is your setup (what CMDT records do you have in place) and what kind of test are you trying (is this an insert? An update? A delete?).

The most helpful information for me to be able to assist would be to upload a debug log here after toggling the “Is Rollup logging enabled?” checkbox to true on the Org Default Rollup control CMDT record. You can save and download a log like this by having your Salesforce developer console open while performing DML on a record as you are testing.

i am very happy to help assist you in getting this to work — looking forward to hearing more.

[pyao-bwc]

Hi @jamessimone , thanks for all your writing and this package! I'm looking forward to using it.

I'm just starting out and trying to get this rollup to work via trigger in a scratch org:

The trigger is simple:

I see that when an opportunity changed from something to Closed Won, Account Revenue is updated as expected.

But if I update the Opportunity to something else like Closed Lost, the Account isn't updated. Here's the log for that (hopefully I got the right level and log):
apex-07L7i00000Jk5YGEAZ.log

If I edit the opportunity again (without necessarily changing anything), Account Revenue is updated as expected:
apex-07L7i00000Jk5dVEAR.log

Running Recalculate Rollup works fine.

FWIW, before reproducing in the scratch org, I tried writing an apex test in my sandbox. That passed, and I couldn't figure out why the test behaves differently.

Do you know where I might be going wrong? Thanks again!

[pyao-bwc]

Hi @jamessimone , one more try! I'm trying to use COUNT DISTINCT to roll up the distinct Products that match a description to the Account.

I have two OLIs:
SELECT Id, Opportunity.Account.Number_of_Products__c, Description, Product2.Name
FROM OpportunityLineItem

It works fine when I update one to be counted. But when I update the second OLI to have a matching description, the count isn't updated:
apex-07LDJ00000DsY3O2AV.log

COUNT works as I expect so far, and CONCAT DISTINCT behaves like COUNT DISTINCT.

For the distinct rollups, I would have thought I'd see a SOQL statement in the log to get the other OLIs under that Account since Apex Rollup would have to know if this was a new product or one already counted. But I only see an Opportunity and Account query. Do I understand it right?

Thanks!

[jamessimone]

@pyao-bwc I will take a look ASAP and see what's going on here. There should be an additional log entry in there for "retrieving additional calc items" as you've said, but it's missing for some reason.

[jamessimone]

@pyao-bwc I've created #411 to track the issue you've reported here, and expect to release a fix for this in the next version of Apex Rollup. Thanks for reporting!

[jamessimone]

@pyao-bwc this issue should now be resolved with #412 having been released.

[pyao-bwc]

Thanks @jamessimone , that worked for me!