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

Hello, I am interested in having the capability to establish "conditional visibility" rules for fields within the interface. Our workflow frequently involves tasks that necessitate varying sets of fields based on the specific project. Currently, our options are limited to either creating separate interfaces for each project or displaying all available fields in the "Task Detail" section. It would be highly beneficial if I could implement a rule that allows fields X and Y to be displayed only when the project is set to B. ... View more

What is the proposed idea/solution? I'm trying to use an interface to present financial information; however, numbers are left aligned in list view and there is no option for totals. Even columns that are right aligned in Grid view are left aligned in List view. Can this be corrected so that it allows the option to right align? How does is solve the user problems? It will allow us to use list view for financial information in a way that is more intuitive to users. How was this validated? ... Who is the target audience? Everyone and anyone that looks at financial information in a list view or interface. ... 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

What is the proposed idea/solution? It should be possible to use detail view templates across interfaces if they are based on the same table, e.g., I have one interface that shows products and one interface that shows tasks and tasks are linked to products. Within the product interface I allow users to click into the details of the linked tasks and currently I have to recreate my task detail view across interfaces. How does is solve the user problems? I'd save time as I don't have to recreate detail views that I've already set up // I wouldn't have any discrepancies between detail views.  How was this validated? We have this issue constantly and are experiencing increased workload through this Who is the target audience? Builders ... View more

Overview: We cannot create new Linked records when submitting a form. There is only the ability to create a new Linked record after the initial form is submitted (and record created). This is not conducive to some workflows, where it would be very helpful to create a linked record during the initial record creation process. Feature Request: Allow users to directly create linked records while they are in the process of submitting the initial Form/record in Interfaces. Current Workarounds: Provide a link on the initial Form for a user to open up another form to create the linked record prior to them completing the initial form. Create additional fields in the table and then use automations to automatically create linked records in the background when those are selected.   ... 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