Hey @JonahM ,
Welcome Airtable Community !
The way to do so is exactly like you described it. Have another table with the names, you shouldn’t have different fields for every name. Instead. you can link that to a 3rd table, and in this 3rd table you link the company and the name and the amount.
Let me know if this helps.
Best Regards,
Mohamed Swellam
Hey @JonahM ,
Welcome Airtable Community !
The way to do so is exactly like you described it. Have another table with the names, you shouldn’t have different fields for every name. Instead. you can link that to a 3rd table, and in this 3rd table you link the company and the name and the amount.
Let me know if this helps.
Best Regards,
Mohamed Swellam
thanks Mohamed!
I don’t exactly follow though.
First table will be Apple and Netflix in records. What will the fields be there?
What should be in table 2 and 3?
thanks Mohamed!
I don’t exactly follow though.
First table will be Apple and Netflix in records. What will the fields be there?
What should be in table 2 and 3?
The first table is Netflix and Apple
2nd table is Investors, technically just a name (or you can add the info you need of course).
3rd table is Investments, this will be linked to the first table and the 2nd table.
Here is a draft of the tables.
this 3rd table is what we call a Line Items table.
The first table is Netflix and Apple
2nd table is Investors, technically just a name (or you can add the info you need of course).
3rd table is Investments, this will be linked to the first table and the 2nd table.
Here is a draft of the tables.
this 3rd table is what we call a Line Items table.
wow - thanks!!!
really, really appreciate it!
The first table is Netflix and Apple
2nd table is Investors, technically just a name (or you can add the info you need of course).
3rd table is Investments, this will be linked to the first table and the 2nd table.
Here is a draft of the tables.
this 3rd table is what we call a Line Items table.
@JonahM - the advice given is exactly what you need to do … possibly a transactions table so every new purchase or sale of a stock is recorded and linked to 1) the stock and 2) the investor.
You will then find it easier to mark date, stock price etc and therefore to understand the portfolio value etc with formalae.
So record 1 could be
Name: Transaction 1
Investor : linked record to Investor 1
Stock: linked record field to stock 1 (eg apple)
Transaction type: buy / sell
Price : currency field
Volume : number field
The price will be a static field when the transaction was processed
You will then have stocks which can have a life price field (possibly pulled in via an API) and linked to every transaction that is included
You will also have individuals with the data on them - inc email
Because you have linked fields you will be able to see the quantity of each stock held by each person and the purchase cost / sale price, current stock, current value , profit / loss etc.
@JonahM - the advice given is exactly what you need to do … possibly a transactions table so every new purchase or sale of a stock is recorded and linked to 1) the stock and 2) the investor.
You will then find it easier to mark date, stock price etc and therefore to understand the portfolio value etc with formalae.
So record 1 could be
Name: Transaction 1
Investor : linked record to Investor 1
Stock: linked record field to stock 1 (eg apple)
Transaction type: buy / sell
Price : currency field
Volume : number field
The price will be a static field when the transaction was processed
You will then have stocks which can have a life price field (possibly pulled in via an API) and linked to every transaction that is included
You will also have individuals with the data on them - inc email
Because you have linked fields you will be able to see the quantity of each stock held by each person and the purchase cost / sale price, current stock, current value , profit / loss etc.
super, got it now Russel, thanks!!
your explanation is really clear
The term for what you need is a Junction table as the others have mentioned
Here’s where Airtable explains more about how and when they’re used:
