Hi, im trying to build an app for real estate investors. Each investor allocates money in a property. Properties can have multiple investors, each of them owning a % of the property. Also investors can have multiple investments in different properties, and they should be able to access their portfolio. Investors are not supposed to see other investors portfolios. Im not sure how to structure the tables, can someone help out? Its a bit confusing relating the tables since I think there is a many to many relationship involved (each property has multiple investors and investors invest in multiple properties). I was thinking on creating a separate table for each property, containing the payment information, and another table for the investors. But im not sure how to link the property tables to the investor tables. Thanks!!
That would be a maintenance nightmare.
On a surface level, I recommend an Investor table, a Property table, and an Investment table.
- Investor table will list the Investors, information about them, and have row owners applied.
- Property table will have information about the property.
- Investment table will have Property ID, Investor email, and additional info about the investment for each investor. It will also have row owners applied.
From there, you have a few options depending on your intended app flow. Here’s some random thoughts to consider.
- A relation linking Investment to property, following by several lookup column to bring property information into the investment table.
- or, create a relation linking investor table to investment table using email. Then create a lookup to return property IDs. Then create another relation using that lookup array to link to the properties.
- or, create a relation linking property to investment using property id, and then add lookup columns to bring investment info into the property table.
3 Likes