v1.6.20 - Null Coalesce

• Backend changes to take advantage of the new null coalesce (??) syntax in Apex. While this does not affect the functionality of Apex Rollup, it helps with maintainability by decreasing the overall size of the package

v1.6.19 - Updates Extra Code Coverage Plugin

• Fixes #573 by upgrading Extra Code Coverage plugin
• Improves test coverage for usage of OrgLimits thanks to @jongpie

v1.6.18 - More accurate REFRESH calculations

• Fixes an issue with where clauses beginning with NOT(...) in RollupCalcItemReplacer
• Several enhancements to REFRESH-based flows that help with recalculating rollups with multiple parents from the same child
• Flow performance enhancement - more rollups will now be prevented from going async when there are no matching calculations to perform
• Apex Rollup consumes count queries when determining whether queueable/batch is the appropriate "conductor" for going async based off of Rollup Control limits. This update improves the count-based logic to avoid double-counting children records whenever possible

v1.6.17 - Adds CMDT support for Task/User/Event

Overview

• Fixes #568 by ensuring batch full recalcs that are added to a processing chain end up starting correctly
• Upgrades @jongpie 's sfdx-bummer plugin
• Adds support for Task/User/Event objects to be configured via Rollup Custom Metadata Type records 🎉. This required some updates to the Rollup CMDT layout, as there are now text fields that can be filled out for:
  • Parent Object (Text)
  • Parent Object Rollup Field (Text)
  • Parent Object Lookup Field (Text)
  • Child Object (Text)
  • Child Object Rollup Field (Text)
  • Child Object Lookup Field (Text)
• Added validation rules to ensure data correctness due to the above additions

Task / User / Event (etc...) CMDT Rollups

This update vastly simplifies how rollups for unsupported objects need to be configured, and hopefully makes CMDT the preferred approach for setting rollups up.

Configuring these rollups should be pretty simple:

Note that validation rules will prevent you from setting duplicative fields:

v1.6.16 - Continued Optimizations

• continued optimization work for large batch full recalc operations, particularly those that roll up to multiple parent types from a single child type
• updated CLI version from 2.21.8 to 2.29.5
• skipped a version on the namespaced package so that it and the primary package are now in sync as far as version number goes

v1.6.15 - Continued Bulk Full Recalc Work

• Standardizes prefixing System namespace for logging levels, which was inconsistent
• updates polling time in Full Recalc app from 3 seconds to 10 seconds between polls to minimize number of logs produced while waiting for full recalcs to finish
• fixes an inconsistency across batch full recalc runs where state tracking could fail if parents present in disparate batch chunks - say, chunks 1, 3, 5, etc... - had children qualify in only some of those batches. This has been a complicated and pernicious issue, and in many ways is a return to some prior version of the parent tracking present in prior versions of Apex Rollup. I've added some logging to the end of each batch chunk to monitor how this affects LDV orgs

v1.6.14 - Fixes ordering issue for batch full recalcs to multiple parents

• Fixes an issue reported by @solo-1234 where rolling up 1 child to multiple parents where the parent types keep alternating lead to rollup fields accidentally being cleared

v1.6.13 - Spring '24 updates

• updates metadata to API version 60
• updates batch state to keep track of batch-over-batch updates to parent records on a per-object level
• fixes a bug reported by @solo-1234 where batch full recalcs had the potential to pull back too many parent records, which could lead to inadvertent record clearing

v1.6.12 - Flow Bugfix for Multiple DML

• Fixes #556 by properly detecting when subsequent DML statements enqueued by Flow triggers should react to deletes
• Updates to contributing guidelines
• Re-adds eslint to pipeline - thanks to @codefriar for noticing this omission!

v1.6.11 - Continued Flow Optimizations

• Continuation from #540 with more flow improvements. This is another big update to the efficiency of Apex Rollup when invoked from Flow, particularly for bulk updates
• Fixed an issue reported by Katherine West where logging wasn't re-disabled after outputting the "starting to timeout..." log message
• Adding scopeProfiles property to sfdx-project.json care of @jefersonchaves