To whom it may concern, An enhancement suggestion from Kalypso: Enable inclusion of visual bars for all grouped levels defined in a Gantt View Currently, it only displays the level 1 items in the table Expected Benefits: Enable better visualization of hierarchy of List Views displayed in Gantt View. For Kalypso, the hierarchy is as follows: Level 1 = Tasks Level 2 = Phases Level 3 = Workstreams Please consider adding this capability.  Regards, Jason Knighten ... View more

To whom it may concern, An enhancement suggestion from Kalypso: Add Base Search extension as a standard feature in Data and Interface layers primarily due to Managed Apps do not currently support inclusion of Extensions. If Enhancement #55 is adopted, this enhancement is less critical. Expected Benefits: Ability to access base search as standard feature and with less navigation in both Data and Interface layers. Also to eliminate configuring manually in child apps when using the Managed App solution. Please consider adding this capability.  Regards, Jason Knighten ... View more

To whom it may concern, An enhancement suggestion from Kalypso: Enable inclusion of configured Extensions within Managed Apps. Expected Benefits: Ability to include benefits of various extensions within the Managed Apps capability. Please consider adding this capability.  Regards, Jason Knighten   ... View more

To whom it may concern, An enhancement suggestion from Kalypso: Implement a hierarchy/grouping of the tabs in a Base. To scroll across 10, 20, 30+ tabs is a frustrating UI limitation. And, tabs represent topics that can often be "grouped" into larger, logical constructs of related information. Expected Benefits: Better organization of related information and a better UI experience when navigating tabs. Please consider adding this capability.  Regards, Jason Knighten ... View more

In Form View (and in grid view also), we have some multi- and single-select fields. The selection options tend to be long, and some would need to wrap two lines of text to be displayed fully on form view.  People using the form, can see the full option text of the selection by mousing over, but this is tedious as we have many long selections.  It would be great, if when we create the field, we have the option to "Wrap Text." We realize this may mean that some of the checkboxes will have one line gaps between them, but that is OK with us. We prefer better customer usability.  Screenshot image: Shows long text being cut off.  "Add wrap text toggle option here" image: Where you can put the option to wrap text  ... View more

I am using Airtable and Softr to create a webpage for my nonprofit. One feature that is essential for this app is for the users to be able to edit and view data that is grouped by a particular value (an article's name, in my case). I find it very frustrating that Airtable only allows for views to be embedded, which do not allow inline editing, although they offer interface design which does allow for inline editing, but is not supported to embed. Having flipped through Airtable and Softr community platforms, there have been many requests dating back to over 3 years ago now, with no update. One use said "they don't seem to care". If that is the case, I need to find a new platform because this is an essential feature for the functionality of my page. @dashler78 Can you please provide the community with an expected timeline for this feature, or for an explanation of why it is not offered?   Thank you. ... View more

What is the proposed idea/solution? This is a crosspost in the actual 'ideas' forum. I originally proposed this here When opening a record details page (sidesheet/full page), I'd like to be able to press a button to open the same record details but in a different, customized record detail page. I have so many customized record detail pages that I would love to make use of, but the only way to currently do that is in a different interface page, or use the 'open url in record' hack that has to reload the entire page to work, which is a bit clunky. How does is solve the user problems? Simple use case: open record details to view information that is not edit'able, click button to open the edit'able version of the record. How was this validated? I use hacks on every single one of my airtable apps to do this already. Who is the target audience? Honestly, I can imagine just about every interface-builder would use this. It would open so many options. ... View more

I often scroll through the list of 'What should each record be called?' and am left a little flummoxed by the inability to select a custom 'name' for records. For instance, 'Template' doesn't exist, though I often have a table dedicated to Templates. 'Prompt' is another one, which I often use to store AI prompts. I imagine it's a bit of a slog putting together that massive list of potential record naming conventions, so if possible, could you let us create our own record 'names' for records in a table? As an extension, could we have variable record names which are defined by a single select field? This one's a bit more unlikely for you guys to implement, but I often reuse tables that have the same structure for multiple types of records (ie. Quotes and Invoices, or Time Blocks and Shifts).  Anyways thanks so much 🙏 ... View more

What is the proposed idea/solution? Allow the Button field type to be used as a Prefix field for List View, both in interfaces and base How does is solve the user problems? I use list view often for a list of hyperlinks. I then make a button field open the URL. Currently, I just organize the button first, so that works fine, but it'd be nice to have a prefix field be a button option. How was this validated? I press button and I become happy. Who is the target audience? People who like buttons before text ... View more