Hey, I completely understand where you're coming from, I faced similar frustration when I first started using Clay. Over time, I realized that Clay sits somewhere between a spreadsheet and a database, with Postgres as its underlying foundation. Since we're so used to traditional spreadsheets, it’s natural to expect similar behavior from any table interface. But Clay is designed differently.
If you’ve ever used Microsoft Access, Clay is quite similar in how it structures data. The constraints you’re encountering are mostly due to the inherent limitations of SQL-based systems, which introduce a learning curve, but one that Clay University does a great job of addressing.
To answer your question: a good practice would be to import each sheet as a separate table and then create a third table that pulls data from the other two. Just make sure you're mapping columns of the same data type when merging.
If you’re curious to learn more about Clay’s architecture, I found this article insightful: https://refactoring.fm/p/clay
.png){kind=logo}
