Tags: jamessimone/apex-rollup
Tags
v1.7.5 - Advanced Currency Bugfixes (#655) * started tweaking PMD rules to allow graceful cutover to new scanner when the time comes * Fixes #653 by ensuring MSP values are parsed correctly when using `INCLUDES` * Possible fix for #654 - was not able to repro this locally, but I'm guessing the update will fix the problem reported * Fixed a weird date literal bug with Australia time zones due to oddities with `toStartOfMonth().addMonth(1)` logic * Added a possible fix for #651, as well
v1.7.4 - Allow Cursor Usage From Batch Apex (#648) * Fixes issue reported by internal colleague with RollupCalcItemReplacer when two rollups with parent-level fields use mutually exclusive where clauses on the same parent-level field * Fixes #646 by providing escape hatch for cursor usage when batch apex is the originating point for Apex Rollup
v1.7.1 - Scheduled Rollup Updates & Date literal comparisons (#641) * Fixes #640 by properly ensuring RollupDateLiteral comparisons occur in local time since they are always based off of the running user and their time zone * Fixes an issue brought up in #639 where scheduling a rollup can inadvertently exceed the max query rows
v1.7.0 - Improve Memory Management for LDV Full Recalculations (#636) * Actual fixes for #615 - this time with 100% better memory management! This involves a cutover to Database.Cursor as well as a DataWeave script * Fixes #638 by addressing a classic DST issue in RollupDateLiteral. Slight cleanup of RollupFinalizer and RollupParentResetProcessor
PreviousNext