Introducing Interface Designer 🎉

Not that I’ve seen. I actually was just trying this again yesterday and didn’t see that function.

Thanks for the info. And yes I’ve checked Stacker previously but the pricing for the functionalities I want is quite steep for our department.

I completely agree. It’s not priced to the market for my client’s applications.

A couple of things on my interface use.

• The entire interface reloads for a few seconds after I start typing. Waiting it out is one thing, but my text entry location losing focus is a real pain. I keep my interface open the entire working day, and as it’s a private base I don’t understand the need for this loading routine that executes multiple times a day. Often I am on the phone entering information from that conversation but having to wait for the reload and reposition my cursor.

• Could a method be added for a persistent note area, so that as I cycle through records, the persistent text area stays the same? Been thinking about this a lot lately. It’s like I need two side-by-side record views open… maybe I just do that in two different browser windows. :thinking:

I agree! Being able to publicly access these interfaces would be extremely beneficial. Let’s hope as soon as it’s coming out of beta that it will be available without an airtable account - and that a couple of these interfaces will be available on the free tier as well.

Stacker is way too expensive! If Airtables just allowed Interface designer to be used like how shared views are used. this would be awesome.

Agreed!

Not sure why that’s the case…

Looks like it might be closer. At least they said something about the go to base button going away.

And now old apps are called extensions so interfaces could be the next no-code apps Airtable step.

Hi,

I submitted a couple of bug requests for this this morning, but also wanted to post here just in case, because it is an urgent problem that needs fixing as it is interfering with the work I can do in AirTable today. The bug I am referring to is when you add a field to an interface page, the “editable” button is selected but you can not edit the field. I tried to select “View-Only” to see if toggling it would make it work and it would not. So it seems the toggle is stuck on “editable” and the field is not editable. Below is a screenshot of what I’m talking about. The top objective field is the field in question was added this morning. The bottom objective field was added yesterday before I experienced this problem and that is what the top field should look like. Please fix this ASAP. I’m unable to publish my interface pages I’m building without it. And I needed to publish them today! Please help.

I saw this too, I assume this will be fixed shortly, in the meantime. If you duplicate an existing editable record and change it to the field you want, you can edit it.

Thank you for flagging this! Confirming that a hot fix will be out for this today :slightly_smiling_face:

Thank you, I appreciate it!! Looks like it’s fixed now!
ᐧ

Good morning @Jordan_Scott1 ,

When you have a moment, could you check with the team regarding if an “OR” operand is planned for the Interface Filter Element? We just hit a very big snag after discovering a Filter Element appears to be hard-coded to “AND”, whilst also disallowing Conditional Groups… it’s a real problem. :thinking:

Screenshot below.

I suspect as a workaround, I can guide the user possibly to use the TimeLine View via a base, which will allow for “OR” filtering… I think… I hope. :expressionless:

EDIT: As a workaround, thankfully the TimeLine View within a Base doesn’t have this same limitation. I’d consider this feature mission critical for the success of using Timelines within an Interface - hopefully it can be patched in soon.

Thanks for flagging this, @Karlstens

I’ve just filed an escalation internally about this - will keep you posted!

With this change, the Record comment thread is no longer rolling up comments on attachment fields. is this intentional?

Greatly appreciate your help here - I’m hoping that we’ll see the familiar options found within a Base Table Filter, including And, Or and Filter Group features - that can then all be used in the same manner within the Interface Filter Element. Fingers crossed… :crossed_fingers:t2:

I’d also love that! The pivot table is really missing in the interface designer.

Hi kuovonne.
Can you share the background automations?

Erk, I’ve just realised that the Link Record Grid Element doesn’t allow for the creation of new records :sob:

This makes it next to useless. :cry: And the default Link Record Card element is a few too many clicks in comparison with lots of white space… functionality it’s OK, but I suspect that the Grid would be a lot more desirable to use in most cases - assuming the Add Record lock is resolved.

Yes, it is very unfortunate. I hope they can get it fixed

This limitation is the one thing keeping me from using Interfaces for my business, which would otherwise be a huge productivity booster. I’ve made a thread about it before but adding/duplicating records through linked record grids doesn’t seem to be very high up the priority list.

I do hope this feature is going to be added soon.

@Karlstens - We use interface button + script automation to get around the add record grid limitations. Just a few lines of script to get running.

// get source record ID that we want to add. Configure as input for your code within automation.
const sourceID = input.config().sourceRecordID;
const parentTbl = base.getTable(‘ParentTable’);
const childTbl = base.getTable(‘ChildTable’);
const parentRecord = await parentTbl.selectRecordAsync(sourceID);
if (parentRecord ) {
// create new child record and link to the parent ID.
let newRecordID = await childTbl.createRecordAsync({[‘ParentField’]: [{id:parentRecord.id}], });
}

Yah, buttons and their individual Automations are a lot to develop, track and maintain - and although I haven’t checked, when an Interface button triggers an automation to create a record, I assume that records Created By field would then read “Automation”, rather than the user who clicked that mock-up “Create Record” button?

Perhaps Airtable Devs are needing bugs to be solved before they unlock these features, but it just seems strange that we have all the options users needing via the Right-Click menu, it’s just they’re greyed out.

I’m concerned that they’ll remain locked/greyed out forever due to system limitations? Would be good to know what’s going on here, before I commit time to developing work-arounds.

Isn’t there some inconsistency when creating records from the Interface Designer? When I create a new record from the record list I can specify the form design and which fields are required, but if a new record is created from a record picker (creating a new linked record) I have no control whatsoever on the corresponding design and required fields. Am I missing something?