Your Sheets made more clear the type of data that you have
Now i’ve understood your concern about “one big database” for all the credit card, this is because your data are .csv formatted in different ways!
Ok! So, your idea of having 2 or more different tables is the easiest way to import your data, then, to see those, you need a little trick
As now on coda, if you want you can filter and “manipulate” the data in one table as you want (and this will be perfect for your case if you had one single DB)
The pathway of your data in this case will be:
2 Sections, one called DB (that contain the raw table with all your data) and a second one that is “Dashboard” (where the same table is viewed [i mean, a view of that “DB” original table]) that contain your filtered data according to a category selector.
So, this is the base, now, we have to apply the same concept to more tables, and this is tricky.
To obtain that we must create a Second (third or more, when i say two, second ecc i’m refereeing to 2 credit card, if you have 3,4 or ecc just apply the same concept) table that “Aggregate” all the different tables you have.
This table will have “TOT”/“X” (numbers of different credit cards) columns named “Name of the transaction - visa” (or whatever), this column will be filled with rows from his own table, according to your selected category, thanks to a filter.
Let’s say that we have a column, named “Name of the transaction” also in the original table (or tables)
In this row in the Raw DB you have (for every tables for every credit card) a name of the transaction (or an id or something unique), if you want to put those rows into the “Summary - Dashboard” tables made before, you can’t just use [creditcardvisa].nameoftransaction because you have to mix more than one tables in one column…
You have to aggregate all the “Name of transaction” columns for every credit card in a “name summary column” that will act as a link to the original table, summarizing the other column in just one.
Then, in another column, you can use
to recover your useful data from your Other tables.
(if different tables that are configured in the same ways, like date columns are all called “Date” between the different credit card tables, it’s not for sure that they will work, i’ll tell you more, they will 95% not work right out of the box)
I’m pretty sure that it’s easier if you are a newbie to create a single table called “Transaction DB”, using it as a single source of data, if you do not want to use this approach because it’s messy to convert your credit card data into a single universal layout, remember that before or after you have to compare those different datas, so, or when you are importing those or later when computing those, you have to do the “stupid” job of making those comparable.
It’s harder to understand written concept instead of a live doc, if you could provide me some more specified datas (because we are talking about more different table, one for every credit card, but you gave me one single table to contain all of those…) i can create a basic sample that show this concept.
Do not stop trying! Coda have to be used to be understood really!