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

This would solve many issues with ‘New’ records disappearing in Kanban Views (because they don’t meet a Filter requirement). Would also make Airtable a fierce task management tool (finally!) ... View more

I love having the Locked View feature to lock the structure of the view for my employees. However, it is only the structure I need to lock and would still love to be able to have filtering functionality within a locked view. Thank you. ... View more

Issue: It’s difficult to find the corresponding View for a Share View Link, especially in Bases with many Views that have Share View Links created. Solution: Make a utility to reverse lookup a View from a Shared View Link that would indicate the Base, Table, View. Thanks! ... View more

Hi, I’d like to see some advanced form view options: Full page-width forms; Editable font-size; Radio buttons for Single Select; Check boxes for Multiple Select; Number limitations (i.e. Between 1 and 10); Sliders for numbers, percentage etc.; Character limitations on single line text and long text. FYI: Using it for tests with the possibility to choose between answers. Currently using the drop down options form users to choose between Answer A, Answer B, etc. Because there’s more text than a simple form in it, the current form-width in combination with the somewhat ‘big’ font-size, makes the form harder to read. Besides that, it’s easier for users to fill in radio buttons, than to select from a dropdown menu. Best regards, Bram ... View more

Hey everyone. When you have a large set of records, grid view with grouping / filtering / sorting is a great way to create reports and surface meaningful insights. The problem for me, is when I have to turn this view into a PDF document that looks professional. A- Page designer, is great for adding headers, logos etc but it doesn’t support embedding a grid view with grouped records etc… and it only works with single pages. B- On the other hand, printing the grid view creates a very raw layout without headers or titles… I would love to see a report designer block with the ability to customize logos, headers but also border styles and fonts for a grid view Hope I’m not the only one wishing for this one… ... View more

What is the proposed idea/solution? Labels for Fields within the Grid View. Form Views have them, but we need them in Grid Views too. How does is solve the user problems? Similarly to a Form View, I'd like to see Field Labels available for use within the Grid View. Labels become overly useful when tables are busy with countless fields that result in having complicated names usually to cater for schema and base design. But such complex Field Names become disconnected from their audience - such as when a Grid View is created, specific fields are shown (with their complicated base-design related field names) and then that view is shared/embedded with the read-only audience. The audience is left to consume the shared data with those awkwardly complex field names. One workaround is for the base designer to post-adjust those complex field names to something more simpler for their target audience - but this only works when the data is being consumed via one Grid View. If the field is to displayed (yet represent different data, thanks to clever/efficient base design), then the name must be left ambiguous to cater for the multiple views where that field is visible. Another workaround is to spin up many formula fields with the desired field name that simply reference the other complex fields, but this strikes me as bad design and I can't justify employing such an ugly workaround. To help explain this dilemma further - take my current hobby project for my local running club where I have a field called "Fastest Runner". Due to all the events, time fields, position fields, roll-ups and lookups, field name needs to be detailed for base design - such as "Fastest Runner (from Event) (excluding volunteers)" - or something similar. From there, this field is used in many Grid Views, four of which are exposed on the clubs website via Embedded Views - which is where the problem is. Four embedded Grid Views 10km - Mens Results 10km - Womens Results 5km - Mens Results 5km - Womens Results All of these Grid Views display Fastest Runner (from Event) (excluding volunteers) , but really, each one of them needs to have this name adjusted for the audience. Perhaps I'd like each view to have the field labelled as; Fasted Male Athlete Fasted Female Athlete Or maybe, Fasted Male 10km Athlete Fasted Female 10km Athlete Fasted Male 5km Athlete Fasted Female 5km Athlete And interestingly, this functionality actually exists (!) but only within the Form View - unfortunately not in the Grid View. Can we please have Field Labels available for use in the Grid View, where they'll be visible within an embedded view as the fields name? ... View more

Even though it is such a small thing it is extremely annoying to work with. I would really appreciate it if it would be possible to have the option to start every calendar view on Monday. Ideally, it would be not only for the browser but also for the mobile and desktop app. (Changing the browser time zone does not work) ... View more

This hurts Kanban view to me, as it prevents me from easily seeing the full task name. It’s cut off regardless of the primary field being a single line text field or long text field. Perhaps a compromise would be only to display the full primary field if it was a long text field. ... View more