Sorry if this has already been requested, I feel like it should have been by now but don’t see anything out there just yet.
I have several clients who have a great need to see WHO made changes to the record. Because the change is made via API, the revision history in Airtable is not accurate.
Is there any other way to see who/when changes were made to a record in NL? Would be nice to have it similar to Airtable where it’s a toggle between comments and record revision history.
Adding record comments via workflow may be a workaround option, but definitely not scalable nor does it allow for granularity on the field level changes.
Yup! We’re hurting on this too - team members breaking stuff or not performing duties correctly and I can’t hold them accountable without an audit log - not good for information systems - short-sighted
Hi @darragh - This would be a great functionality to add - would benefit all users.
I have the same issue as @Brandi_Bullock. The AirTable record revision history states, ‘You edited via API (using Noloco integration),’ so it is missing the user details needed from an Audit perspective.
As you say, it would be even better if it was available in NoLoCo.
One way to workaround this and to keep the history is to have a field called Updated by text and then have a workflow in Noloco that runs every time a record is updated.
Then you would add the name of the Noloco user who updated the record to it so you would see the existing Airtable activity log, plus the value change to that new user’s name / email.
I am looking to implement this, but I am hitting a roadblock. I’m not doing something very basic correctly, and I can’t identify it.
I have set up the new ‘updated by text’ field in AirTable (single-line test) and run a manual sync.
I created the workflow to run when a record is updated and selected all relevant fields to watch.
I then set the Action to update a record, but when I search for the newly created field, I don’t see it; only numeric and formula fields are selectable.
While this is a good workaround for records with infrequent updates, on records that are constantly getting updated, this would be HEAVY in workflow usage and challenging to pinpoint the changes made.