v.1.6.10 - Rollup Conductor tweaks

• Fixes #551 by tweaking logic and docs for how batch/queueable apex is used to start up the async portion of Apex Rollup

v1.6.9 - Fixes "No such column 'Field__c' on entity 'Object' error"

• Prevents RollupParentResetProcessor from attempting to reset fields on different parent objects

v1.6.8 - Fixes NPE

• Fixes #549 by preventing NPE

v1.6.7 - CDC updates

• Added support for undelete in CDC triggers
• Updated expectations in a few CDC tests to more properly align with what actually happens in the CREATE and GAP_CREATE change types
• Fixed an issue with Flow where REFRESH flows that pass Parent Record Id For Empty Children Collections with the result of a non-matching Get Records input reported by Katherine West

v1.6.6 - Continued Flow Improvements

• Continued flow optimizations
• Added new Parent Record Id for Empty Children Collections property to invocable actions to support resetting parent fields when there are no matching children. Must be used in conjunction with Child Object Type When Rollup Started From Parent due to flow collections not passing the child object type natively
• Further RollupEvaluator improvements
• Fixed an issue reported by jcart where multi-currency orgs with LDV and ACM could occasionally overflow the sync heap size when fetching dated currencies

v1.6.5 - Flow Optimizations

• fixes #539 by optimizing the update code path for rollups started by Flow

I expect there are additional optimizations that can be made to the Flow side of the Apex Rollup code base - these changes came as low-hanging fruit after several days of analyzing log files, but they're certainly not an exhaustive improvement.

v1.6.4 - Scheduled Flow/Job bugfix

• Fixes an issue discussed in #532 (and possibly #533) that was affecting some scheduled runs of Apex Rollup due to a serialization issue with the newer System.AccessLevel enum
• Added a test proving that #537 already works

v1.6.3 - Reparenting Bugfix & Grandparent Rollup Full Recalc Bugfix

• Fixes #523 by correctly grouping all grandparent records into ordered batches
• chore: sfdx to sf cli upgrade, project files, dependencies (#535) contributed by @dschach
• Fixes #514 by properly detecting when reparenting operations should decrement when used in conjunction with where clauses

v1.6.2 - Intermediate Grandparent Bugfixes

• Fixes #514 by retrieving now-orphaned grandparent records when an intermediate lookup is changed and there are no further connections to the grandparent
• Fixing DST literals
• Adds additional logging to assist with #523
• Updating Is Full Record Set helptext
• Fixes #530 by detecting intermediate grandparent deletions

v1.6.1 - Intermediate Grandparent Reparenting fix

• Optimizes sort algorithm for ful lrecalc datatable in Apex Rollup app
• Fixes wildcard support for LIKE where clauses that don't just start and end with %
• Fixes #526 by adding support for subscribers stipulating the lookup field on the parent record when using the Recalc Rollups LWC button and properly querying non-Id fields for parent when RollupParentResetProcessor runs
• Part of #518 fix by properly detecting intermediate grandparent reparenting from Flow - the updated grandparent now recalculates properly. More work to do to fully close this one out by properly recalculating the old grandparent record
• Query optimization while investigating #527