Skip to main content

Hey everyone,

In my databases interface section I have two interfaces containing several list views, that are of course referring to the same data. The first interface is ment to be for typing in data in our planning process and mostly used from desktop devices. The second interface is for executing purposes and is mostly used on mobile devices on location. This interface should be read only.

Summarized:

  • When we are in the office, we are planning and typing in data in the first interface.
  • When we are out of office, executing jobs, we log in to our accounts an our mobile devices to read the condensed and important data.

BUT:

What we are faceing is, that it seems, that within the interface section of our data base alle lists behave the same in terms of a field being read only or being editable.

In easy words: When I change the status of a field from read only to editable in one list in the interface section it does this not only in this list, where I am changing it but in all lists, that show this field! But why? It makes no sense at all! What am I doing wrong?

Couldn’t find any hints, of how to avoid this or why this happening. I hope sb here can help me. :-)

 

Hey ​@lennartaekta,

That should not be the case. To make sure we are talking about the same things:
Airtable calls “Interfaces” to the whole front end user experience.
However a given front en user experience can have multiple Interfaces, and each interface can have multiple Pages

My understanding is that you have two different interfaces, each with a given List page layout. Right?
If so, the config (fields show, filters applied, edit inline allowed or not, etc) for the list itself should be completely independent. That is when discussing the list itself, which looks pretty much like a table.

However, the tricky part comes if you are talking about record detail pages. If you allowed clicking on a given record to expand its details, then that is where you will need to pay attention as you can (i) use the exact detail page for records from the same table (this is default, and probably your case), or (ii) use different detail pages for records from the same table depending on what page you are accessing that detail from.

Please see screenshot below for further context.

 


If you need any help setting this up, please make sure to grab a slot using this link and I’ll be happy to get this solved for you on a 5 min call!

Mike, Consultant @ Automatic Nation 
YouTube Channel


Hm, could you provide some screenshots of the two Interfaces and their setup options like the following screenshot please?

I just tested this out with the following toggle and it worked as expected, I had two List interfaces, one that was editable and one that wasn’t, tested it on mobile

 


Reply