Both the Portal and Interface include the In-line Editing feature, where records can be edited directly on the grid, similar to the experience of editing records in Airtable.
Inline editing is enabled by default for new extensions when their plan supports portal User Actions. To turn it on for your existing portal or interface, you need to go to:
Tables
Click on the table of your interest
Under Views → Default View Settings, set View Type to Grid
Go to User Actions and turn on Inline editing
If any of your views are set to use custom view settings (under View Type), this setting needs to be configured for each of those views separately (under User Actions).
With this feature enabled, the records will be editable directly on the grid:
Clicking on the 'Open' link will open the child form.
Computed fields will be calculated and updated in the grid while you edit the fields. Summary fields will also update accordingly.
Limitations
Field validation is disabled while using inline editing.
Adding new options to select fields is not supported outside of the child form.
Fields with conditional fields or options can only be edited through the edit form.
Dynamic filtering will not be applied to linked record fields when inline editing.
Linked record fields with static filters are not editable inline.
Because the inline linked-record editor has no dynamic-filter value picker, rules that disable adding or removing records when the filter is empty restrict the corresponding inline action. Disabling additions alone does not necessarily prevent removing existing links.
💡 Tip: While the Inline editing feature doesn't offer the functionality to copy and paste records directly in the grid to create new rows in bulk, if the data exists and can be modified in Google Sheets or a similar platform with public CSV URLs, you could use the CSV importer extension to periodically transfer the data to your Airtable base. This could facilitate your workflow if it relies on working with spreadsheets and moving large amounts of data to Airtable.
For formatting differences and workarounds, see Rich text fields: limitations and workarounds.