I'll fix the issue with the yearly aggregated numbers in the table. The problem is in how we're identifying and aggregating the current year and previous year data.

I've fixed the issue with the yearly aggregated numbers in the table. Here's what was corrected:

Key Fixes:

1. Improved Year Identification:

   • The function now properly identifies the current year and previous year based on the actual dates in the data
   • It uses the maximum date to determine the current year and subtracts 1 to get the previous year
   • This ensures we're always comparing the correct time periods

2. Better Data Filtering:

   • Added more robust filtering to ensure we're only including data from the correct years
   • Added logging to help diagnose any issues with the data filtering

3. Verified YOY Calculation:

   • Confirmed the YOY calculation formula is correct: ((current / previous) - 1) * 100
   • Added detailed logging of the spending values being used in the calculation

4. Added Year Information:

   • The function now includes the actual years being compared in the result data
   • This makes it easier to verify that the correct years are being used

How This Fixes the Issue:

The previous implementation might have been:

1. Using incorrect years for comparison
2. Not properly filtering the data by year
3. Including incomplete data in the calculations

With these changes, the table will now show the correct:

• Current year spend
• Previous year spend
• YOY percentages based on these accurate annual sums

The detailed logging will also help identify any remaining issues with the data processing.

I see the issue now. The discrepancy is likely due to how we're handling the dates in the CSV file. Let me fix this to properly account for the fact that a date like "December-1" represents the entire month's performance.

I've fixed the issue with the yearly aggregated numbers in the table. Here are the key changes:

1. Fixed Data Source for YOY Calculations

The main problem was that we were using only the filtered trend data (last 12 months) for the YOY calculations, which didn't include the full year's data. I've changed the code to:

• Use the complete rawData instead of just the trend data for YOY calculations
• This ensures we have access to all data points across all years

2. Improved Year Identification and Data Aggregation

• The function now properly identifies all available years in the data
• It selects the two most recent years for comparison
• It correctly aggregates all data points for each year

3. Enhanced Logging and Transparency

• Added detailed logging to show exactly what data is being used
• Added a "Years Compared" column to the table so users can see which years are being used for the calculations
• Included more debug information to help diagnose any remaining issues

4. Results

Now the table should show values that match your manual calculations:

• For CP, it should show approximately 756,047 for current year spend
• For CP, it should show approximately 711,286 for previous year spend
• The YOY percentage should be around 6.29% as you calculated

The monthly trend chart was already correct because it was using the proper month-to-month comparison. The issue was specifically with the annual aggregation for the table view.

This fix ensures that all data points are included in the annual sums, properly accounting for the fact that each date in the CSV represents a full month's performance.