This update is most welcome. Thank you so much for sharing!

( I had actually stopped using/developing interfaces due to this very feature being locked for so long. Now I have some work to do! ) 🥳

Thank you very much for this feature!

Yes! Been looking forward to this one for so long!

Deleting a record works by right clicking on the record in the gridd view that is added as an element, but it doesn't workin a "show data as grid" view (I can only "copy" and "expand" and everythin is enabled in the right hand settings bar). Am I missing something? 

@Jan_Segier1 hmm, that doesn't sound right.  Can you verify that the "Add/delete records inline" toggle is enabled in the "Add Records" section (see screenshot below)? 

Aha, it said "enabled", but had to click through to toggle "add/delete records inline" seperatly. Works fine now, thanks. 

Thanks, long awaited feature.

However, it seems that when a user without base access tries to add a record in an "embedded" list in an interface, they get a "you are not permitted to perform this operation" error.

Is there a solution to that issue?

Excellent features that are necessary for Interfaces to be a top-tier useful tool. Thank you!

Some feedback on an issue that these new features exacerbate, at least for me. It seems that various ways to create interface elements that list related records are increasingly inconsistent in their features and UI.

For example:  

• A list view created from a page template has options to be a List, Gallery, Kanban, Calendar, Timeline, and Grid and it can have New REcord and action buttons:
  
• However, a linked record field in a record detail pane -- showing the exact same content -- would have additional options to be displayed as Pills or Cards:
  
• However, if I create a page using the Record Review template and add a linked record field, I can only display those as Pills or Cards:
  

   

• If I choose instead to create a Grid/Cal/Kan/Time/ or List, then I can switch between those layouts, but the UI for both editing and for the user is different:

  

  • Here now settings are all over the place and dramatically different:

    • Permissions settings are in different places
    • the "list options" submenu of settings is not there
    • there's an appearance tab in one bt not he other
    • I can't let users switch between visualizations/layouts in one 
    • There are not tabs/dropdowns in one verison.
    • the UI for users adding a new record is different between the versions
    • I can't add action buttons in one variant ....
    • etc etc etc

       

In short, it seems as if there are multiple versions of elements that are largely displaying the same data, each with different settings and capabilities. This introduces a lot of friction for me when I'm building interfaces. It in particular it makes experimenting with different approaches to display data cumbersome and frustrating, forces me to remember multiple locations for the same/similar settings, and has user-side UI inconsistencies that make their experience less consistent. 

It would be helpful if features and settings on such similar elements could be kept in sync with eachother as the Interfaces Designer product is developed and updated over time.

This is a great update, but @Johari_Wiggins pease could you confirm if the below is expected behaviour, and if there is a further update coming to allow full creation of linked records:

I'm trying to create a record, and within that create a new linked record. There's a nice new 'Create a new [object]' button, but rather than brining up a form/further modal like you might expect, this just creates a completely empty linked record which then can't be edited:

... that seems kind of weird?

I then tried starting to type the name of the customer as if I was searching for them, and this then fills in the name in the 'new object' button, so I guess that's the purpose of the button:

... but this seems a slightly unintuitive workflow (perhaps the button shouldn't appear until you type, if that's the intention) and you still can't fill in any details for the new linked record (other than the record name).

Further to that, if you use the form method (which would be my preference), there's no option to create a new linked record at all - seems inconsistent?

I appreciate the update nonetheless, and I know it's a complicated product with lots of feature requests to balance, but I'm just wondering if the ability to create a linked record (with additional field inputs) through this type of workflow is something that's being worked on? I explained the issue here on a community thread, and also emailed the support team a couple of weeks ago about it. I can't work out if I'm missing some solution, or if this is just a limitation and, if the latter, if I should hold out for an update.

Thanks! 

@Yaron_Avramov this is an issue we are currently working on. It should be resolved in the next week or so.  In the meantime, you can avoid this issue by adding the parent linked record as a visible field in the "embedded list". For example, if you're looking a project detail page and add a Grid element for the project's tasks, you would need to make the 'Project' field visible in that Grid. Not ideal, but hopefully this can unblock you enough as we resolve this issue!

@dsolimini I hear you, I can see how that inconsistency is confusing and adds a lot of cognitive load.  I will pass this feedback along to our product team. 

@wkidger ah yes, the creating of a blank record is a weird UX.  I will file a bug on our end for that. I don't know of any plans currently to support triggering creation forms directly from Grid element but I can see how this would be useful. I will bring it up with our team. As far as creating linked records within forms, I know that's something we've discussed but I don't believe we are actively working on it at the moment. I'll be sure to mention this as well. Thanks for your feedback!

This is Great!

However Id like to add my voice to the list of those finding it still a bit of confusing and sometimes frustrating disconnect between how some features can add records vs those that rely on the form popup.

This seems to be related to inline methods or fields allowed to access the records for specifically select type fields or connected record fields allows ability for user to add new options to these fields. However Any method were the add a record uses th form popup adding new options to these fields is not an option or possible.

For instance you can have an inline add record where when enabled an editor or collaborator can add a new record to multi select, single select, or connected record fields. This ability too add options that dont already exist is really really valuable, however in some interfaces like record view adding a record uses the form interface to add records and this wont allow you to enable or add new options for any of these same fields. This can be pretty confusing and frustrating in limiting options for builds when you wnat users to be able to add new options.

I prefer the slide out record creation vs the form because of this ability but allowing it for forms or not defaulting to from input are not options currently would be great additions to make function feel universal. the most at odds example is the Record review interface. You can have an element field fully open to creating new options by the user yet if they use the panel to add a new record you can on of those same fields. considering how often a formula field is needed to be the primary field this is pretty frustrating

I would like to also ask why the option to add a record from a form when in a grid view is not an option?

I have invoices that I need to add line items to, I don't want my user to have to click add a blank row and then edit it with the record pop out... I want them to be able to add a linked record (via a form) and fill in the details required at the click of a button.

Whilst I appreciate the new ability to add new records inline I still would love the ability to add a template record OR a record from a form or choice of forms. This is applicable across a lot of applications and I wonder why it is not a key feature in you development.

The ability to add a link record to the current active record is a sort after feature and one that I've had to turn to other tools like softr, on2air and clucky form automations with slow re-directs that should be a native feature in Airtable.

I don't want to give users an extra step to add a row and then edit it - they can do this in other ineterface layouts (list views etc) but not when in a record and looking at linked records.

ESPECIALLY when I can do this with a card view but not grid or list view (the preferred way to see linked data)

Please Please consider adding the add via form options to list and grid views in record overviews (record review and record summaries)

Thanks for the reply @Johari_Wiggins and for taking the feedback onboard - much appreciated. 

My use case feels like it must be pretty common, so I'm sure there's a workflow/workaround that I'm missing here - are you able to point me in the right direction? Basically what I want to happen is:

Data structure:

• Orders table with order details e.g. total value, items, service date *and* linked field to...
• Companies table, with basic company details (name, address), list of orders *and* linked field to...
• Contacts table - contact details (phone, email, name) - company may have multiple contacts e.g. finance, sales etc.

Workflow:

1. User is viewing some sort of list/table view of orders. Phonecall comes in with customer wanting to create order so user clicks some 'new order' button to create a new order record in a modal/slide-out/form/whatever.
2. User starts to fill in order detail fields, one of which is the company making the order. This is a linked record field, but since this is a new customer they need to create a new 'Company' record - so a further modal or whatever.
3. User fills out company details, one of which is another linked record field - Contact (they will necessarily have to add a new one in this case) - so another modal.
4. User saves contact details and - this is key - is returned to the half-complete 'new Company' modal.
5. User finishes & saves new Company record and is returned to the 'new Order' modal.
6. User finishes & saves new Order record and is returned to the Order list view where they began.

I appreciate this is several layers deep in terms of creating nested new linked records, but actually on the face of it seems a pretty common CRM type workflow, so I'm wondering how other users are achieving this?

Thanks,

Will

Many thanks for this feature.

Hi!

I just want to point out that if your users don't have access to your base, they won't be able to add new records inline even if you grant them the possibility to do it.