What is the proposed idea/solution? Having the ability to clear unpublished changes on the interfaces has been very helpful, and is  in line with many of other development environments I've used.  In case I'm not being clear, I'm referring to the little blue dot (see below) letting us know the page has not been published, where moving the mouse pointer to the right bring up options including the clear changes.     My concern is when you have enabled "Allow users to open Record Details" when they select a record in many different views.  This will open a Sidesheet (or full page view) of the record, which can be customized.  The problem is that there seems to be no way of clearing changes in this view, once you're made the change it's done, and if you go to the the main page and use the clear changes option it will not clear these changes. To further complicate things, the Record Details sheet is shared for every page that points to that table, so an inadvertent change will show up in multiple pages. Is anyone aware of a way to "Clear Changes" on a Record Detail sheet?  Thanks in advance for any feedback or advice. How does is solve the user problems? It would provide a safety net when making changes and eliminate the time required to recreate and test a Record Detail sheet if it gets overwritten and saved in error. How was this validated? Unfortunately a collaborator was experimenting on a page and new they could restore the main page but was unaware that the restoration would not apply to the detail page. Who is the target audience? Users of Interface designers, particularly those designing interactive pages and interfaces. ... View more

In addition to Grid, Gallery, Kanban, etc. I’d like to be able to do a custom layout for a view-- resizing record fields to optimize their visual display. (Does anyone remember Bento? It was, functionally, similar to AirTable and it would allow you to customize the layout of data views with drag & drop fields that you could resize and place into single, double, or triple columns). It would work sort of like the AirTable block Page View but it would be a view I could share with collaborators and it would be responsive to different size screens. ... View more

What is the proposed idea/solution? It seems likely that this is already being developed, but I suggest adding a new feature to the Button interface element (see attached screenshot for expected location) that allows users to apply a record template to the current record. This enhancement would help streamline the process of creating sets of sub-tickets and eliminate the need for cumbersome automation currently in place. How does is solve the user problems? Allows for faster, easier deployment of records in an Interface. Simplifies base administration. How was this validated? ? Who is the target audience? People using Interfaces with a concept of 'sub-tickets' -- probably other use cases. ... View more

In Interface charts I would like to be able to: Stack line graphs (i.e. turn them into area graphs) Stack line and bar graphs as percentages Plot min, max, mean, and median of a single column all on one chart together ... View more

Using Interfaces, when you bring in a record it will only show a few details in the “card” view, regardless of how wide it is. You should be able to modify the width of each of of those similar to how you can change the width of columns in the normal base so you can view more information at a glance in a view like this. In this example, there is a lot more info we would want to see, but it only shows the first few pieces of data, in this case Order, Year of Release, and Artist ... View more

What is the proposed idea/solution? Change the colour of an entire column like you can do in Excel or Sheets so that it stands out How does is solve the user problems? It is a SIMPLE and MASSIVE UI shift for the user. It allows you to clearly see things that stand out. How was this validated? ... Who is the target audience? ... ... View more

Instead of click click and click, why not implementing sidebar navigation! Kindly take a look at how fibery.io or monday.com implement their UI navigation! ... View more

For Interfaces, can we make the comments field fixed at a height and then it scrolls. I’m finding when the comments box gets really long it throws everything out ... View more

What is the proposed idea/solution? When viewing a record's comments in a base, any comments made against an attachment also appear, as in the attached image. When viewing a record's comments in an interface, comments made against an attachment do not appear, as in the other attached image. I would like the record comments in the interface to behave like it does in the base. How does is solve the user problems? Though it is very convenient to be able to comment directly against attachments, it is inconvenient for the person reading the record to view all of these different attachments to find comments they may or may not care about. The record's comment should be the central place to find comments. This is how it currently works when viewing comments from the base and I would like it to work the same way (at least as a configurable option) for interfaces for the same reasons. Asking Interface users to check multiple places for comments isn't friendly. ... View more