Bug Report

We have identified an issue where the total value is being miscalculated whenever a new data entry containing a value that should be excluded (based on 'Not In' filter) is inserted. This issue arises specifically in the context of count aggregation.

Interestingly, when the configuration is altered and then reverted to its original state, the recalculated total value is correct. This suggests that the issue might be related to the initial calculation process when new data is inserted.

Steps to Reproduce:

Codesandbox link

Expected Result:

Expecting the system to accurately calculate the total value, excluding entries specified in the 'Not In' filter.

Actual Result:

The system is miscalculating the total value by incorrectly including entries that should be excluded under the 'Not In' filter. This miscalculation is resulting in an illogical and incorrect total value, especially noticeable after the most recent update.

Environment:

• perspective@2.7.1
• codesandbox