This user's problem is exactly the kind of friction that makes people feel like their data is working against them, not for them. And the workarounds they tried, FILTER formulas that vanish when the source sheet resets, VBA scripts that grab only the last row, are the hallmarks of a tool that was never designed for the way people actually use it. The real issue here isn't a missing formula or a broken script. It's that traditional spreadsheets treat data as a static snapshot, not a living record that accumulates across years.
What this user needs is a system that understands intent. They have a master sheet that resets annually, yet they need each item-code sheet to preserve its history indefinitely. That's not a quirk; it's a common pattern in inventory, project management, and order tracking. The requirement is simple: when a row in the source sheet contains an item code, copy specific columns to that item's tab, and never duplicate or overwrite what's already there. A FILTER formula can't do that because it recalculates from scratch every time the source changes. A VBA script can do it, but only if it's written to handle multiple matches and avoid duplicates, which is harder than it sounds in a legacy environment.
This is where an AI-native spreadsheet changes the game. Instead of forcing the user to write complex scripts or wrestle with formula syntax, the tool should let them describe what they want in plain language: "When a row in the master sheet has an item code in column G, copy columns C through K to the matching item sheet, and don't copy anything twice." The system then handles the logic, scanning each new or changed row, checking for existing entries, and appending only what's missing. The user doesn't need to know whether that's a trigger, a query, or a background process. They just need the result.
What makes this case so telling is the yearly reset. The user is already planning for a workflow that spans multiple years, but their current tools force them to manually freeze data before wiping the master sheet. That's not a technical limitation; it's a design failure. A truly modern spreadsheet should treat data as persistent and versioned, not fragile and erasable. The goal shouldn't be to find a clever workaround for a broken process. It should be to eliminate the broken process altogether. For anyone managing recurring data cycles, whether it's annual orders, quarterly reports, or rolling project logs, the solution isn't a better script. It's a tool that evolves with your data, not one that resets every January.