Hello Steven,

Why not just create a “Notes” table with a timestamp, long text and contributor field, and create a multiple-entry link between your two tables ?

Seems like this would solve your needs.

Then I’d have to name each entry which is more thinking. I just want to assign a note under a contact.

Starting with Barnaby’s idea of a “Notes” table:

You can use a Long Text field as the primary field of the “Notes” table. That way, you put the notes directly into the primary field, rather than having a separate primary field for a name. It’s worth nothing that, while tables work best when record names are unique, Airtable doesn’t require names to be unique.

Almost feels quick and dirty…

But that’s another table and another field that needs to be hidden in either the company, deals, contacts or tasks tables I have. Plus I want to be able to write the notes directly to the record, not create a record then associate it (have to find it first).

By having it associated with the record directly, I only have to create one relationship then it pulls in all data from it including the notes.

I wouldn’t mind creating a separate table but for the need to name each and every entry.

I’m currently using the comments sidebar but this isn’t searchable or filterable and you can’t collate the notes into a related table (contacts -> company).

The separate table could have only one field. No need for a key.

Now how would you collate all the notes related to all contacts related to a company

So imagine Company_1 has multiple contacts related to it (Contacts table) -

Contact_1|Contact_2|Contact_3

Each contact has multiple notes related to it (Notes table)

Contact_1 - Notes_1|Notes_3|Notes_5

Contact_2 - Notes_2|Notes_4

Contact_3 - Notes_6

What I want is to look at a Company_1 and see in chronological order -

Notes_1|Notes_2|Notes_3|Notes_4|Notes_5|Notes_6

Ah. Yes, for that you would need at least a ‘Contact’ field next to the note.

You could lookup the company for the contact and create a note view grouped by the company.

Right now there’s no default way / function to group it all together in one ‘Long text’ field for example.

In the company field, I can lookup notes related to a contact (also related) but there is zero formatting, it doesn’t recognise line breaks for example.

Now that would be useful!

Yes! I soooo need this as well!

2.5yrs later, I’m now using AirTable, and I really need a “dated notes” option for records. In my case, to track my activities associated with a record. eg. Job application: when i chased them, what they said when they replied, when I chased them again. Or an Action Log, with brief notes recording “progress update”, when an action is reviewed. Seems to be a common request, but no built-in solution. I’ve only found clunky solutions, using a separate table of “notes”, which then have to be linked into the appropriate record. Is there a better way now?

I know this thread is years old at this point, but this is an issue that I have been wanting a solution for for years! The activity sidebar is amazing for taking notes because it stamps the comment with the time and who made the comment, and you can send an alert to people, etc. But when viewing your base from a high level, you can’t easily see when the last comment was made on a record or what the comment on the record was. Please, please, please add this feature!!

Agreed – this seems like an absolutely essential feature. Really wish it was available.

Commenting again because I really want this feature! Also, I feel like I should have clarified another issue with the way it works now. I LOVE that you can @ someone, so that it send them an email alert to look at that record. However, once you @ someone, they get marked as watching that record, so they get an alert EVERY SINGLE TIME you do something to that record. This creates a “boy who called wolf” scenario, where they are getting alerts that don’t apply to them and they have to wade through those alerts to see which ones apply to them. Or, even worse, they just start deleting their alerts without reading them because they are getting too many that don’t apply to them. Other people on your team should ONLY get an alert if the admin for that base marks them to receive all alerts OR if someone else on the team @s them.

For this reason, we built a workaround solution that lets you use a long text field for comments, so users can only add new comments to the field but not delete existing content.