#DLRS Package토론 중인 항목 0개

Thanks, @Rick C

! Full Calculate not working gives us something to start with. That takes a bunch of things out of consideration. Is it that nothing is changing or that the rollup value is wrong or that it is always leaving an empty field? 

Remember, we're ignoring the realtime problem for now. It is almost always simpler to troubleshoot the Full Calculate, fewer moving parts. 

After starting Full Calculate, are you applying any filtering on the start screen? (It gives you an opportunity for a WHERE clause to limit which parent records are updated) 

Can you check the Setup => Apex Jobs page once you start the Full Calculate? You should see a RollupCalculateJob Apex class as a Batch job. It should have a number of batches with it. If you monitor that it should progress through all the records. Depending on the number of parents it needs to recalculate it might take a bit. Let us know how many batches it needed and roughly how long it takes from start to finish. (It should show the start and end times in the list view) 

Will you check if it completes without any errors? If it encounters an un-handled error then it should report that error in the batch job's status. If it is a contained/handled error then it should email whoever started the job as well as add records to the Lookup Rollup Summary Log object. 

I would start by watching the Batch job then if that looks good but still doesn't produce any results I would check the Lookup Rollup Summary Log object next. 

Please report back if everything looks clean or if you find any obvious problems. You may need to look at the modified dates on those log objects to make sure you're dealing with recent outcomes.

@Shaher Cardona

lucky thing the code for DLRS is open and publicly viewable. 

This is the only Invocable action in DLRS. It doesn't have any constructors on it at all. Reading the release notes it is not clear to me if that could be a problem. 

As with most things, enable it in a Sandbox and confirm it behaves the way you want.

@Michael Kolodner

thanks, that makes sense.  

I had an issue last night where like 11,000 rollup up summary log records caused an issue with another process and trying to figure out why. (well I know part of the answer, but still trying to figure out the rest, as issue has got to do with a managed package that is still using a PB that I can't "see", so I don't know what's causing that to fail, which in turn is impacting the rollup. It's never happened before, so I am guessing the vendor made an update which is causing issues....)  And I am making sure that some of my early rollups I made, make sense...

@Dodi Friedenberg, very odd behavior. I don't know why the new wizard would be so different. "Read Timed Out" suggests a problem talking to the Salesforce API but both wizards talk to the same API endpoints, and I think using the same code.

I think the most interesting is the parent does not exist error, like it is collecting the wrong value for the renamed object... BUT in your org that isn't renamed it does the same thing.

I can't think of anything off the top of my head that tells us what is going on. Any other insight or tests that might surface more details?

Hi @Patriece Wright,

Unfortunately The FeedItem object doesn’t support aggregate functions in queries. Other way of doing above would be querying for FeedItems into a collection and checking the size in apex. Make sure to add any appropriate filters to the query to narrow down the results

List<FeedItem> fiLst = new List<FeedItem>();
fiLst = [SELECT Id FROM FeedItem WHERE Type = 'TextPost'];
system.debug("FeedItem Count:"+ fiLst.size());

@Antonija Mihic, "already running" state is tracked in a "Rollup Jobs" custom object, you can look at the age of the record and possible remove it if you think it isn't related to any actually running jobs.

In theory the jobs should have cleared it out when they were finished, if it isn't really running then it likely means the job failed for some reason. You can look through your Apex Jobs around the time time as the record was created to see if there is anything indicating failure.

If the record was fairly recent, you can again look in the Apex Jobs. I think those are exclusively created for Scheduled Recalculation jobs or performing a Full Recalculation.