There's a quiet elegance in what this user is trying to do, even if the immediate result is a frustrating blank cell. They're not just moving numbers between columns; they're designing a system where data follows meaning, not position. That's the entire point of a linked spreadsheet, and it's exactly where most traditional tools start to creak. The formula they tested, INDEX with MATCH, is the right instinct. It's the standard reflex for anyone who's learned that hardcoded references are a trap. But the empty result isn't a failure of intent; it's a signal that the spreadsheet's assumptions about names, spaces, or even hidden characters are getting in the way of the logic.
What's worth noting here is that the problem isn't the concept. It's the friction. The user knows what they want: transfer scores from "DV Score" to "DV Final" based on a member's name, regardless of how the ranking order shifts between tables. That's a sound, practical goal. The fact that MATCH returns nothing suggests something as simple as a trailing space, a non-breaking space, or a name that looks identical but isn't. In a guild roster full of stylized usernames, this is not a rare edge case. It's the everyday reality of managing real people's data. The tool isn't wrong to demand precision, but the user shouldn't have to become a data detective just to get a score to carry over.
The deeper takeaway is about resilience in how we build these small systems. A single formula that works today is fine. A formula that breaks silently tomorrow, because someone edited a name or reordered a row, is a liability. The user's instinct to link by name is correct, but the execution needs to be more forgiving. That might mean using TRIM to clean inputs, or INDEX with AGGREGATE to avoid errors, or even a simple SUMPRODUCT that can match across quirks. The goal isn't to make the spreadsheet smarter; it's to make it more reliable under the messy conditions of real use.
So here's what we'd say to anyone facing this same wall: your approach is right, but your formula is only as strong as the data it references. Check for invisible characters. Test with a single known name. And if MATCH keeps failing, don't abandon the logic, just add a layer of cleanup. The spreadsheet isn't rejecting your idea. It's asking you to be just as precise about the names as you are about the scores. Fix that, and the transfer will happen every time, no matter how many times the rankings shuffle. That's not a workaround. That's the craft.