The issue is that in interfaces, the search feature hides rows of data that do not contain the keyword you are searching for in a grid view. This limits your ability to search and compare all rows of data.    This feature is possible when you use the search function in a data table but not in an interface.   ... View more

Within an interface, when creating a new record via an element - such as Calendar, Gallery or Kanban, there's a pop-up that greets the user that often isn't actually desirable, and if I'm honest, can be a very real pain. Shown below is the pop-up in question, in my example, it's showing a formulated field - and I have no interest in detailing the records other fields from within this pop-up. I can't tell you how frustrating it is (especially for a record-creation intensive workflow) to constantly dismiss this pop-up that seems hard-coded into these elements - especially for records that contain formulated primary fields - this pop-up is extremely undesirable and serves no purpose. It should also be noted that we don't necessarily want to be giving an option to the user to "Open in base" either, assuming the pop-up is to remain enabled. Interestingly, not all elements "Create Record" action/button show this prompt, and in my case I really really really wanted to use the Gallery Element, but having this pop-up makes it a deal breaker, meaning I'll probably be reliant on the List View to achieve the desired outcome - as it doesn't have this pop-up when clicking new record. For context, my users are needing to create a couple of records, and then they can click into them directly via the element that displays the records - a sidesheet slides out for them to enter in the details for that record. And it's in this context that this interim pop-up makes zero sense, and we're needing a toggle to disable it. The toggle option to disable this interim pop-up should be found with the option that enables the record creation button. There should also be a toggle to hide "Open in base" if the interim pop-up remains enabled. ... View more

What is the proposed idea/solution? Allow for accent colors to help distinguish expanded records from each other.   How does is solve the user problems? Sometimes the all white background makes it a bit confusing as to what the user is looking at.  Would be nice if base could have customized accent colors to help distinguish different elements. How was this validated? Allow for color to be selected for any expanded records.  Who is the target audience? ... ... View more

What is the proposed idea/solution? I would like the ability to have the header be visible on every expanded records so when I scroll down it will continue to show it--and users won't lose their place.   How does is solve the user problems? Allow for long expanded records to be visible.     ... ... View more

I would like the ability to have the header be visible on every expanded records so when I scroll down it will continue to show it--and users won't lose their place.   Example: NOW:   PROPOSED:   This will allow to show important record items on the top, like the legacy expanded.       ... View more

Button field in table can be used to run a script but not an automation. Button in interface detailed view can be used to run an automation but not a script. Besides, these buttons cannot be displayed on record lists. Could Button field be used to start an automation (the same way interface button does)? It could be very useful to have the same button, launching the same automation displayed in different interfaces and in the table views. And also having the button available in lists views. My "hacky" workaround for now, is creating a checkbox field and an automation that runs when the checkbox is checked (and unselect itself at the end). Thanks! ... View more

While it's possible to autofill a "User" field type using the "Current User" that's logged into an Interface, it is not possible to auto-link a Linked Record using the currently logged in user.  Use case: We have a custom table of our users that contains a number of fields including the user's email address. We would like to have the option to autofill (set the default value) of a linked record to the current user that's creating a new record in an Interface form. Currently the user has to select themselves out of the list and this adds an extra step to creating a new record and introduces opportunity for data entry errors (e.g. mistakenly selecting a similarly named user) Example 1: Shows the properties of a User field where "Current user" is selected as the Default Value Example 2: Shows the properties of a Linked Record where there is no option to use the Current User as a default value to auto select the correct linked record. ... View more

When you choose a list interface, there is the ability to sort and filter the data.  However, if you choose the list element on blank canvas the there is no ability to sort. Also sorting on grid view in blank canvas would be very helpoful ... View more

What is the proposed idea/solution? The new open records/expanded records in the Interface designer is nice, but I miss having a floating header that I can always see when i scroll down the page. How does is solve the user problems? Sometimes my open records have a lot of fields, it would be helpful to have a floating heading / head bar so you can show certain fields always at the top. How was this validated? Just a separation like in the legacy version Who is the target audience? Work Flow users ... View more