Replies: 1 comment 2 replies
-
@jdids247 bulk data loads should definitely invoke Apex triggers. It's hard to speculate on what might be happening without more info though. For example: has the org Rollup Setting been properly configured? Is there a user or profile level exclusion that would affect the user doing the data load? Typically, one way to validate things would be to start a trace for that user under the Debug Log section, do a small data load (preferably with Is Rollup Logging Enabled set to true on the Rollup Control CMDT org default record) and ensure in the logs that are created that Apex Rollup is being invoked correctly, and that there aren't issues updating the parent-level records for that running user or something. |
Beta Was this translation helpful? Give feedback.
-
New Apex Rollup user, so bear with me if there is a known setting that fixes this.
We use this on the OpportunityLineItemSchedule object to get the MAX Schedule Date and it's revenue number. We then update the OpportunityLineItem record the schedule is tied to.
Everything is working great when the data in the OpportunityLineItemSchedule is updated or added from the GUI, but we just had a user bulk load in schedule data using Data Loader and it didn't fire off the rollup. I can see the jobs completed in the Apex Jobs log
We're using CMDT-based trigger on the OpportunityLineItemSchedule object to kick this off
Here's the CMDT
Here's the trigger
I hope I'm missing something obvious here.
Beta Was this translation helpful? Give feedback.
All reactions