I'm creating a script that reorganizes linked record field values across the whole base using alphanumeric sorting. I ran into something that looks to be a limiting factor from how Airtable works but would like to pose it to the community to confirm....
Asking users to structure their base in a way that is conducive to Airtable's best practices falls short (requires workarounds like automations) when they would like a single form to contain EVERYTHING they need to capture during the intake process.A...
Airtable's power really shines when structuring a base in a relational way. In my experience working with many new Airtable users, this is not always immediately obvious and takes education (especially for users coming from Excel). Instead of requiri...
What is the proposed idea/solution?Update the roll-up field to return expandable linked record values when rolling up a linked record listHow does this solve the user problems?The roll-up field currently returns comma-separated text when rolling up a...
Hi @catherinepope,The event label that appears in an external calendar app will be the primary field of the synced table. You can't change the primary field from view to view but you can adjust what appears in it (such as combining multiple fields) u...
Hi @Sara,I would ask for some unique identifier as a question on the form (such as email address) to compare with an existing contact list when the form is submitted. You can set up an automation withthe trigger "when form is submitted"a Find Records...
Could the selected record associated with the button click or automation test not have email values populated?The "When a button is clicked" automation trigger requires the button to be placed on an interface page that contains either a Record Picker...
The easiest way I can think of would probably be adjusting editor habits to always include valid times in the date entries for both tasks/meetings. Task end dates could be EOD (unless a hard deadline is a meeting or something else).You can enable tim...
Rather than copy data across tables, it would be better to have one Projects table and separate Live/Recommended/Onboarding/etc. project categories with views. This way you can ingest data into the table that belongs in and not have to consider/maint...
