Appreciate the ability to bold, italicize, and strike through text in long text fields, and to format as headings, numbered or bulleted lists, etc.  It would be very helpful to be able to highlight text as well, or at least change the color of the text. Change in text color, at least, must be possible as hyperlinked text appears in light blue.  Our particular use case is a shared legal research database, where our long text field is the notes each lawyer takes on each case.  It would be very useful to other researchers to see highlighted passages.  We currently use bold text, but it doesn't really stand out in a helpful way. Thank you.   ... View more

What is the proposed idea/solution? To have the capability to send a page designer form to a record  How does is solve the user problems? The page designer currently only supports printing as an export option, if I were able to export to a record that would be incredibly more efficient. The current way to attach a page designer document to a record is by "printing" the doc, then saving as a pdf, then uploading to a dedicated attachment field. I should be able to send a doc straight back to a record in my base.   How was this validated? ... Who is the target audience? I'm currently using page designer with interfaces for my fulfillment use case, it has some serious potential if a litte more work was put into it. ... View more

What is the proposed idea/solution? Allow tabs ('\t') and newlines ('\n') in the prompt argument to input.textAsync. How does is solve the user problems? Multiline prompts would make longer prompts more readable. The following is, quite frankly, a mess: How was this validated? Tabs and newlines in the prompt string are not shown. The above mess is generated by the following code:     const grps = ['Update Projects entry', 'Topic', 'Database', 'Results', 'Dev build', 'Initial meeting', 'Demo', 'Data sharing', 'Contouring', 'Model development', 'Interim analysis', 'Final analysis', 'Study proposal', 'Study protocol', 'Grant', 'Prospective data collection', 'CRA', 'REB', 'Abstract (will be published on its own)', 'Manuscript', 'Poster', 'Presentation', 'NDA', 'Privacy/security review', 'Cover letter'].sort(); var origPrompt = 'Record group to create. Choose a number.\n'; for(var i = 0; i < grps.length; ++i) { origPrompt += (i + 1) + '.\t' + grps[i] + '\n'; } origPrompt += 'Group number: ' await input.textAsync(origPrompt);     Who is the target audience? Users who want more formatting options in scripts, especially for longer text prompts. - Note that this wouldn't be an issue if radio button inputs were supported. ... View more

What is the proposed idea/solution? ... Have the chance to apply different conditions and/or filters to columns (like lookup) in different views. How does is solve the user problems? ... At this moment, the only way to apply different conditions to columns is to duplicate the tables and apply the new condition or filter. If we had the chance to create different views with better control of conditions and filters, we would be able to reduce the number of tables and have everything in the same table but with different views. Why do we need different conditions? if we want to apply automations and scripts is easier if we are able to filter the data and the columns in views. We can apply the automation to that specific view. Who is the target audience? ... Everyone that works with multiple kinds of products, clients, locations etc, and wants to analyze data based on a specific feature.  ... View more

My automations would be much easier to maintain if, instead of duplicating an automation for each possible trigger, I could have an action in another automation that triggered it. For example, I would like to send a certain email any time a button is pressed, and also under certain conditions if a form is submitted. Instead of having two identical automations with different triggers, I'd like to have: one automation based on the button press that sends the email (and does nothing else), and a form-triggered automation with a couple actions (unrelated to the email) and a conditional action that triggers the button-press automation to send the email.  ... View more

What is the proposed idea/solution? When populating automation filters there is the option for choosing a static value or a dynamic value. This would be great to add ability to switch between static/dynamic values in regular View filters... How does is solve the user problems? I currently have a large number of fields used to compare data in 2 fields and flag when something doesn't match for example. It would cut down greatly on the number of fields I have if I was able to use the dynamic setting and adjust my View filters to say if Field 1 does not equal Field 2, then show in this view.  How was this validated? ... Who is the target audience? Smaller teams needing to manually QA various datapoints without the need for additional field counts... ... View more

What is the proposed idea/solution? Include interface access on Android phones and permit form creation for any type of phone. Or, making the app available on the Windows store in some capacity for PC users.  How does it solve the user problems? This would make experience more consistent across all platforms. Interfaces are extremely helpful for transmitting information and using on site for a job. We can set up on the back end in preproduction a clean interface with information that is constantly changing. But, when only 50% of the freelancers we hire have the same kind of phone, it becomes a hindrance in efficiency.  Who is the target audience? Anyone who doesn't have a mac or an iPhone. Google Pixels and Samsungs are becoming more prevalent because of availability and pricing, Airtable needs to step into the PC world with accessibility. It will change the user experience dramatically.  ... View more

What is the proposed idea/solution? To hide the first (main) column of a table in a Grid element. How does it solve user problems? Not all tables' first column is important, especially for tables that mainly connect between linked records. While the first column cannot be hidden on Airtable base tables, it should be possible on the Interface Designer's Grid element. Who is the target audience? Those who use the Grid element on the Interface Designer. ... View more

What is the proposed idea/solution? To be able to group Interface Designer's pages into sections. Additionally, to access them via hover/clicked dropdown or mega menu at the top when the Interface is published. How does it solve user problems? If a user has multiple pages in the Interface Designer, the user should be able to group them into different sections for a cleaner, more organized view. Like data table views having sections on the left, pages should, too, as they act as an alternative to table views. Who is the target audience? Interface Designer users. ... View more