Last modified time [SOLVED]

[Katherine_Duh]

UPDATE 2: last modified time is now available to everyone! You can learn more about it here.

UPDATE: The last modified time beta is now closed as we get ready for a general release. Thanks to all of the testers who made this beta a success.

ORIGINAL POST:

Hi folks! We’re very excited to announce that we’re beta testing a last modified time field type, as well as a LAST_MODIFIED_TIME formula function. Many thanks to the users who’ve posted specific, detailed feedback about their needs and use cases with regard to this feature, like @Arlo_Haskell, @Deborah_Buck, and @Jordan_Friedman. We read everything that is posted here in the forums and your feedback is incredibly valuable for us when we’re planning the product roadmap and developing new features!

If you’re a Pro plan user and you’re interested in testing out the last modified time field type and/or the LAST_MODIFIED_TIME formula function—and giving us your feedback—please sign up using this form. (Note: this is a different form from our standard beta signup form, and it requires you to fill out a couple of additional questions.)

As you are all aware, this is a highly anticipated feature, and there are many users who would like to get beta access. However, for technical reasons and to ensure an optimal user experience, rollout for this beta will be conducted in small, limited batches. (In practical terms, that means that it might take a while for you to get access.)

[Random_Walker]

+1M to make “lastModifiedTime” for each record along with “createdTime” that you have. Why it is being so hard to add this column in your schema? This is so basic feature to have. It would make help to integrate with your APIs. Don’t you store the last modified timestamp already in your persistence layer? All we are looking for is to expose it in the API response as well:

TEST_TABLE record: {“records”:[{“id”:“recNtemt9W2GgTd3J”,“fields”:{“Name”:“test”,“Notes”:“Test 4\n”},“createdTime”:“2018-09-19T22:35:26.000Z”, “lastModifiedTime”: “Please_Provide_this_field__”}]}

This request has been open since 2015, I am surprised to see it has not yet been added to the APIs response over last 3 years. What is the underlying issue which is making it so hard to add this field? Can someone from Airtable team provide any insights on it?

Thanks in advance.

[Nate_Biggs]

+1

Valuable and needed

[Kyle_Bento]

Joining the party. +1 for this feature.

[Matt_Frederick]

Still no update?

We have more people adopting our Airtable solution for product information and this is more and more critical.

@Airtable_Support @Airtable_Team

[Joe_Downey]

Any updates on the progress of this feature? @Airtable_Team @Airtable_Support

[Jose_Waihiga]

+1 to last modified timestamps. Please! At the very least a progress update would be nice :slightly_smiling_face:

[Clayton_Gates]

+1 to last-modified timestamps. This is an essential element for tracking information efficiently. Thank Airtable!

[Andrew_Burke]

+1 … I like to imagine my reply will be the one that tips this over the edge after 3+ years.

[Joey_Seal]

I would pay for airtables if this where a feature

[Blaine_Light]

Any update here? it’s been 5 months… we need this feature as our zaps are breaking all the time when trying to add a timestamp.

Also, @alexanian already wrote the code… how hard is it to do this? https://github.com/alexanian/airtable-last-updated-hack