This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Hi Airtable Team,First off, I'm really enjoying the new Personal Access Tokens feature -- it makes it *much* easier to cross-check which external Make.com scenario is responsible for record/field level changes via the Record History view. Great job!...
Okay, continuing my ask from this original idea:https://community.airtable.com/t5/product-ideas/proper-revision-history-api/idi-p/153234I came across this page in the Enterprise Audit Logs:https://airtable.com/developers/web/api/audit-logs-overviewIf...
How can Airtable Enterprise Audit Logs be sufficient when they exclude record-level revision histories? This seems like a MASSIVE oversight. Am I missing something else here?Original article: https://community.airtable.com/t5/development-apis/readi...
What is the proposed idea/solution?For a selected set of records in a table, generate a report showing all the changes made to those records within a given timeframe, split by user, then split by field.How does is solve the user problems?This provide...
I have spent too many hours working around problems like:Converting comma-separated strings to unique elements in an array/setSORTING elements in arrays/sets properlyComparing to different arrays/sets in order to determine intersection/differenceNONE...
@ScottWorld , that's precisely what I'm talking about. In the Enterprise Service Accounts section, Airtable still calls them "Personal access tokens" (even though they aren't personal -- tied to a service account instead):To be fair, we're in the pr...
Okay, I'm going to take this lack of acknowledgment by Airtable product teams as a sign that this problem isn't getting fixed anytime soon. Therefore, I'm posting my exceptionally ugly hack/workaround for ARRAYDIFF() using none other than my favorit...
This seems like a no-brainer for Airtable to support. To be crystal clear, there *is* an undocumented API that's fetching this information -- it's just not available for 3rd party developers to use. I honestly don't understand how Airtable appears ...
Actually, there might be value in having three variants of UUID():
UUID(Anchor=RECORD_ID()) - the UUID is anchored to RECORD_ID() value
UUID(Anchor=CREATED_TIME()) - the UUID is anchored to CREATED_TIME() value
UUID(Anchor={Field Name}) - the UUID is...
The base I’m working with has many, many linkages across many, many tables (more than 2) – yes, a graph database may have been a better approach (long-term), but I’m forced to manage this legacy implementation.
To answer your other question, I starte...
