Hello everyone,
I’m currently exploring the new Tables feature (really enjoying it so far) and have a question:
How can I replicate functionality similar to lookup fields and formula fields from Airtable?
I understand that Airtable doesn’t follow a traditional relational database model, but I’m curious how to implement comparable behavior within WeWeb Tables.
Thanks in advance!
Hey @Adrian1 
First, you need to create a linked field column in your table. You can link to a user or another table:
And make sure you select a record. In the example below, I created a “Link to Users” column and made sure to select a user for my record:
Then, in a table view (i.e. which is what you’ll bind to an element on your interface), you can select what fields of the linked record are available:
Here’s the full process:
Those are not live yet but the team is working on it 
Great, thanks a lot!! Any idea on when formula fields might be coming to weweb tables?
I don’t have an ETA at this stage. The product team is still heavily involved to decide on the best UX for this and what should be included so I wouldn’t expect it in the next few weeks.
Can you share more about your use cases? Do you already know the type of formulas that are a must-have for you and those that you can live without?
Thanks for the answer, I get that and appreciate the efforts you are making atm.
Regarding the Formulas: I mean it in a way that Airtable formulas are working. An overly simplified example would be a dynamic date field that calculates something like “date1 + numberOfDays = date2” on the backend side.
I know it can be done on the frontend side easily but for some backend automations to run it would be great to have it dynamic and on the backend side.
Hey @Joyce, I have a follow-up question for linked records within the same table.
When I link two records within the same table, I can not select any reference fields in the columns popup.
Should that be possible? Is that a bug? I would love to have that.
(Context: In my case, I have a specific order of tasks that I set up by having each task link to a “previous task” within the same table. That is the core of my task-management-system as I will be able to build a cascading project-timeline based on planned due dates and realistic due dates. Now I choose to do that by linking records so that I can f.e. easily bring the due dates from the linked previous task to the actual task for building a frontend like “show task as pending if previous task is done”. Doing that in the frontend by searching/iterating through the whole task list would be much more resource-heavy, I think.)
Mmm that sounds strange. Not sure if it’s a bug or if I didn’t understand the flow. Could you record a short video to illustrate what you mean? If there’s confidential data, don’t hesitate to share in the support chat instead and link to this thread so the team has the full context of your question
I think the problem can be reproduced easily:
-> I think the problem is because of linking records from the same table to eachother
