I released a custom extension I'd like to utilize in different bases within my own workspace. Is there any way to duplicate the extension in a different base without needing to create a new custom extension and re-lint it?
Maybe Zapier has spoiled me, but it would be really nice to get a little more granular detail on our automation runs within our bases/workspaces. Right now, the only way to see any form of metadata re: automations is to go to individual automation’s ...
We have an Enterprise level account and are trying to implement a date field which will track the date that a status is changed in another field. This is all good on a move-forward basis, but we would also like to update it historically, which is pro...
I have a multiple select field I am attempting to update within an automation, but I can’t seem to add an option to it without overwriting. Pared down, this is essentially what my code looks like right now:
Val = record.getCellValue("The Cell")
if(co...
I tried to use csv import but apparently it doesn’t support importing to long text fields. I have 1100 records I need to populate a long text field for and I would prefer to not attempt a copy and paste here with such a wide margin for error. Has any...
Airtable has a built-in snapshot feature that will provide much more richness than automation in this case! How-to guide here: Taking & Restoring Base Snapshots | Airtable Support(I do want to add that I misspoke when I said revision history would be...
Huge second on this! Would be great to retain the colorful tags and just have a switch to flip that would show only unique tags rather than repeats. I hate losing the visual richness when I have to swap over to a roll-up.Double bonus if this could al...
I would recommend using a back-up of your base; it will be a one-time static copy of everything you have, data, automations, and record history, but won't affect the primary base operations are still based out of.
yeah totally @Katie_Haines !I will say that my solution is limited to when the multi-select field has only 1 argument already entered, you'd likely need to use a switch statement or loop to handle multiple, but the field update ended up looking like ...
