It would be helpful to be able to wrap text within a Formula, Single Line Text or a Long Text field if the column width on view is too small. (Rather than truncate the text)
Welcome to the community, @Alejandro_Marco! :grinning_face_with_big_eyes: Unfortunately there aren’t controls for the kanban view to drive the height of selected fields.
Yeah, it’s surprising that this hasn’t been addressed over the years. Having a UI that allows people to read the contents of the page is a fundamental ux best practice and should be expected at the bare minimum.
Open and clicking details for record sometimes is okay, but when you tag longer answers it’s very painful to do it every single time. Especially if you have more than 10 records to tag!
I am in full support of variable row height as an option and I feel that an extremely useful and standard functionality like this should not be kept from Airtable Customers just to prevent user-error (on a manual choice, no less). I’ve set up up an infrastructure that adds lines for each item of an order, and it’s a smidgen of what it could be because A. There’s an incredible amount of wasted space here and B. If the amount of items exceeds 6 then my team will have to click and expand at least 5 cells, which is just unnecessary. A variable row height option would instantly make this setup buttery smooth and really nice on the eyes to look at and process.
The expanded record view does not help present this data at all, really. It’s a lot of stuff going on, and the expanded record view requires scrolling and occurs in a smaller vertical space.
Through my searches on the forums, it’s clear to me that people really want the dynamic row height feature. Even if we have to go into a hidden menu and unlock this feature, so as to keep people from unintentionally bloating their databases with it, I think a whole lot of Airtable Customers will be very happy.
I am trying to embed content into a public website.
Each embed will contain many records records (anywhere from 1 to 20), so users will need to scroll down to find the one they’re looking for. We do not ALSO want users to have to pop out a record or scroll through the information. The tallest cell option is not tall enough.
Additionally, formulas do not seem to be supported in the gallery view that supports multiline text, and the data is combined from many fields across many tables.
There does not seem to be an easy option to avoid truncation of the text, rendering the embed less than user friendly.
To be clear, formulas are supported in all views. If you need to add line breaks to a formula’s output, insert the \n escape code into your string whenever you want a line break. For example:
To insert line breaks between the retrieved values from other fields, do something like this:
{Field 1} & "\n" & {Field 2} & "\n" & {Field 3}
That being said, there’s still no way to control how the cards in a gallery view appear in terms of the available space for fields containing long text, whether they’re formulas or normal long text fields. You might need to look into tools like Softr that allow you to display Airtable data in a more web-friendly fashion.
The lack of wrapping text is an intentional design decision: to allow wrapping text, we would need to support variable row heights. Our rows are a consistent height in order to avoid the bloated mega-rows that you often find in spreadsheets. Generally, we believe that that table/grid view should be a good overview of a number of different records, whereas the expanded record view gives you the details.
Interesting philosophy. Fails in practice. I think I want this to work like Filemaker Pro! Perhaps I just need to convince my company to switch to Filemaker Pro.
Adding my support that text-wrapping is an absolutely CRITICAL feature of data tables. Without it, I simply can't transition my project management to AirTable. Airtable has some great features, but I can't forfeit my ability to view all the data at a glance.
It's THAT critical, and such a simple concept I can't understand why they haven't implemented it.
