Releases: jamessimone/apex-rollup
Releases · jamessimone/apex-rollup
v1.5.46 - Batch Consolidation, Flow merge bugfix
- updated parent reset button in advance prep for Spring 23 to use
RefreshEvent
instead of the now-forbidden Aura refresh hack - Consolidated a ton of async code related to batch/queueable processes which really trimmed down on
RollupBatchFullRecalculator
in particular - Fixed a bug reported by Katherine West that was introduced in #396 whereby Flows called by imperative Apex invoked from merge operations failed to get the right
System.TriggerOperation
assigned to them - Updated Extra Code Coverage plugin
- Trimmed down
RollupTests
and converted quite a few of its tests that had strayed from the unit-y nature of that class into integration territory
v1.5.45 - Incremental Full Recalc Improvements
- Incremental improvements again being made to full recalcs - this time by ensuring stateful variables are actually being populated correctly when a full recalc is batched
v1.5.44 - Updated most logging levels to INFO
- Updated logging levels to
INFO
for most high-level rollup operations. This allowsDEBUG
to be used to filter down to being able to answer the question "what did my parent-level records look like before/after rolling up?" - Fixed an issue found while investigating #404 where the parent reset processor was occasionally running for full recalcs even when explicitly disabled via
RollupControl__mdt.ShouldSkipResettingParentFields__c
v1.5.43 - Parsing Text-based Date/Datetime Support
- Adds support for rolling up text fields that have date/datetime values in them
v1.5.42 - Async Cleanup
- Prevent too many queueables error by ensuring
RollupSObjectUpdater
does not split updates when in the midst of timing out - Cleaned up some async code paths to continually refine CPU time usage
v1.5.41 - executeBatch Safety
- Prevents
Database.executeBatch
call during full batch recalculations to avoidDatabase.executeBatch cannot be called from a batch start, batch execute, or future method.
v1.5.40 - Enable Logging for Custom RollupControl__mdt records
- Fixes #363 by enabling logging for rollups controlled by something other than the Org Default RollupControl__mdt CMDT record for @solo-1234
- Updating SObjectDescribe calls where appropriate to use the SObjectDescribeOptions to fix new scan violations
v1.5.39 - Flatten bugfix
- Updated README with better LDV information
- Fix issue reported by Katherine West with
Rollup.flatten
method - Fixed a few date literal edge cases that have shown up in the new year
v1.5.38 - Parent Recalc Button bugfix
- fixes a bug reported by Stephen Stanley where the parent recalc button failed if Rollup Order Bys were defined
- trims even further down on heap size usage by clearing a stateful map being used by the batch full recalc processor - it's only necessary to maintain state until a parent record has finished being processed, at which point a ton of heap can be freed up by
- removed a few unneeded enum values for operations like
MOST
,ALL
,NONE
andSOME
since most code paths here follow the same logic - now provide feedback faster (by showing the spinner) when clicking the "Start Rollup!" button on the full recalc app. Thanks to @benblackthorn and @attilah for reporting this issue!
v1.5.37 - Dated Conversion Rate Support
- Created integration testing framework that allows for arbitrary "call and response" polling to take place between Apex scripts, enabling the addition of integration test with 80k opportunities getting rolled up
- Added support for dated conversion rates with advanced currency management