Replies: 1 comment
-
@hammads22 support for this project is handled by a wonderful community of users on the Trailblazer Community Group I'll provide a quick reply here but if you need additional assistance please create a post over there. Generally speaking, make sure you are on the latest version of the tool (v2.22) as there are improvements there. Aside from that, you may need to reduce your batch size. Rollups are calculated based on child records and DLRS needs to pull those records from the database to build the aggregate values. If you have lots of records with lots of children, one record with 50K or more children, or lots of rollups that end up pulling similar data from the database, then DLRS can overrun the platform limit. If you really have lots of data to update then I generally recommend you work with someone on your team that understands this tool to disable the rollups during bulk updates then reenable them and perform a bulk recalculation. (That may still require changing the Custom Setting for batch size of those jobs) |
Beta Was this translation helpful? Give feedback.
-
Hi Team,
When trying to load data into the system, I'm getting 'CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY:dlrs_FinServ_FinancialAccountTa0TTrigger: System.LimitException: dlrs:Too many query rows: 50001:--' error.
I have 50000 rows of Financial Account Transaction to update but only a few rows update and then I get this error. Data is rolled up from Financial Account Transaction To Financial Account
Please suggest how I can fix this. I have tried the 'Aggregate all rows' option but still, it didn't help.
Beta Was this translation helpful? Give feedback.
All reactions