Last Closed Won Opp on Account

[tony-jones-tanium]

Hi Team - We've created a simple Rollup record for calculating the most recent Closed Won Opp on the Account, and populating that ID on the Account. At first we tried this with a Lookup Field on the Account (so the Opp was actually linked, instead of just populating the 18 digit ID), but then also tried populating it to a text field. Neither seem to be working. Any thoughts?

[jamessimone]

@tony-jones-tanium I'd have to get a look at a log to see what's going on - one thing I'd try is updating the Child Object Where Clause to StageName = 'Closed Won'.

[tony-jones-tanium]

Does is help having an excel file of the Logs? I have attached it here.

Just seems odd to only update a single record - so we know its partially working.
report1698269069552.csv

[jamessimone]

@tony-jones-tanium have you tried updating the where clause? It's still showing stagename = 'CLOSED WON' and it may be that the field name not conforming to the API name casing for StageName is causing this issue.

[tony-jones-tanium]

Yeah, thats been updated, and still only the single record has been updated:

[tony-jones-tanium]

I also tried updating the package. Since then, the number of Log Entries has greatly increased, however, its still not updating the Parent Object as it should. Attaching a report of the Error Logs to see if thats helpful.

report1698337012707.csv

[jamessimone]

I'm seeing an optimization here which will help, but I'm not sure it answers the underlying question of why you're only seeing one update get made. I'll include the optimization with the next version. In my own testing of full recalcs, I have the exact same rollup you have setup, and it's correctly rolling up for all parents.

[tony-jones-tanium]

Would there be any issues with the Rollup Operation being "FIRST"? Or anything to do with Rollup Order Bys:

[jamessimone]

I don't think so. As I said, I replicated this exact rollup for testing and didn't have any issues. I think part of the problem is the time out that's occurring, and I've pushed up a fix for this that will come out with the next version.