If you've ever tried to build a cascading dropdown in a traditional spreadsheet, you know the feeling: what looks like a simple request quickly becomes a tangle of nested IF statements, manual FILTER functions, and data that stubbornly refuses to behave. The user who posted this question is not alone. They have a clean table of Italian regions, cities, provinces, and postal codes. They want to select a region, then see only the cities in that region, then have the province and CAP fields auto-populate based on the city choice. That is a reasonable, everyday data-validation problem. And the fact that it requires a Reddit post to solve tells you everything you need to know about the limits of legacy spreadsheet tools.
Our view is direct: this kind of dependent dropdown logic should be trivial, not a project. The user tried FILTER and IF conditions and got nowhere, not because they lack skill, but because the tools they're using were never designed for relational data. A spreadsheet column is not a database table, and a formula bar is not a query language. When your data has natural hierarchies, region to city, city to province, you need a system that understands those relationships natively. What this user is describing is a basic foreign-key lookup, the kind of thing a database handles in one line. A modern AI-native spreadsheet should let you define a relationship once and then build dropdowns that respect it, without workarounds.
What this means in practice is that users waste time fighting their tools instead of working with their data. The original poster's goal is straightforward: make a clean, accurate data-entry interface for Italian geographic data. They're not trying to build a data warehouse. They're trying to keep a list consistent. Every minute spent debugging FILTER formulas is a minute not spent on the actual task. Worse, the complexity of these workarounds introduces errors, a wrong range reference, a forgotten absolute cell lock, a typo in a criteria string, that silently corrupt the data. The solution is not a better formula. It is a rethinking of what a spreadsheet should be.
We believe the future of data validation is declarative, not procedural. You should be able to say "when I pick this region, show me only its cities," and the tool should handle the rest. That means built-in support for relational lookups, dynamic ranges that update as your source data grows, and validation rules that are part of the data model, not a fragile formula chain. The user who posted this question deserves a tool that treats their table as a connected dataset, not a grid of isolated cells. Until then, they will keep writing Reddit posts. And we will keep pointing to a better way.