We use Airtable as a CRM and event management. These uses have been accomplished using separate bases but there’s been a growing desire for this process to be streamlined with an emphasis on leveraging the data already in the CRM. Ultimately, what I’m suggesting is Lookup Fields displayed on a Form View once a Link to Another Record Field is populated. Here’s a use case: CRM has a Table containing contacts with contact information (phone number, email address, etc.) and a Table for an event’s participants. The participant table has a Form View. The first field/question on the form is a Link to Another Record Field where the registrant selects their name. The next field/question would be a Lookup field displaying the phone number found on the linked record. The next field/question would ask if the phone number was still correct. The next field/question could be a question conditionally visible if the phone number was incorrect. We’d then repeat the process for the other data displayed by the Lookup fields. ... View more

I imagine lots of people use Airtables to keep track of ordered lists that they want to filter, reorder, and remanipulate, but ultimately return back to the original ordered list. Further, I imagine that from time to time they want to change how that ordered list is ordered… ENTER THE RANK TYPE! It: only accepts integer values when a number is changed, if increments everything at or above it! A table could even have multiple rank columns for different dimensions! It’s like magic! Orderly magic! ... View more

Ability to have a default value for single select - would be perfect for forms filled by applicants in our HR process. ... View more

In our CRM, we have a COMPANY Table and a CONTACT Table (among others). Within each of these tables, we have a CLIENT view and SUPPLIER view. PROBLEM: EXPANDED RECORDS That said, when I expand a record in the Contact Table > Supplier View, I’m inundated with irrelevant Client-Contact-specific fields (ex. ‘Won Projects’) haphazardly stacked at the bottom of the record. It’s become very confusing and bulky for our staff and, in my opinion, it’s probably a big reason so many of us wish we could ‘link bases’; but I won’t dive into that. PROBLEM: EXPANDED LINKED RECORDS Likewise, when I’m in the Company Table > Client View, and I want to access Contact Info for one of our Client companies, I’ll simply click to expand one of the linked records (linked from the Contact Table). In this case, I’m still inundated with Supplier-contact-specific fields, lumped together at the bottom. Ultimately, we need these gone! SOLUTION I’d love for a given record to expand into a Default Expanded View Preference (i.e. with default visible fields) that was specified during the creation of this contact/record (i.e. every time I add a new record to the Contact Table, I can select what type of record it is [“Client” vs "Supplier]; in turn, instructing AirTable on which fields are relevant to that record). The result, in the above example of expanded linked records — our entire sales team will always see this expanded linked record as a “Client”-specific record, per the records’ system-wide default expanded view setting. DEFAULT VIEW & CUSTOM VIEW PREFERENCE But then (hear me out!), once any given record is expanded, I’d like the option to specify, from a dropdown within that expanded record view, how I’d personally prefer to view that contact/record going forward. For example, the Default View for a given Contact record could’ve been set to “Client” when it was created; but, depending on my department and the info I typically need, I can now select an alternate ‘view preference’ from the expanded record drop-down (ex. maybe I choose “Client Finance Data” or “Client Holiday Gift Info”). Once I’ve selected a new expanded ‘view preference’, AirTable would remember this selection as my new personal default for that specific contact/record. The result — anytime the record is expanded by ME, I’ll only see the info that’s relevant to my work. If I need additional info/fields in the future, I can always change my “view preference” with the dropdown. Again, I think this feature would help to calm people’s consistent request to link bases. I do believe all data can be kept in 1 base, and I’d prefer it that way; but we need more features to help us hide things that we don’t want to see. ... View more

I see that Gantt Chart can now be printed (pdf), how about similar functionality for the Pivot Table!!! With my pivot table always updating to reflect my current month data it would be ideal to pdf a monthly snap shot and compare month-over-month differences and results. ... View more

We would love for there to be a way to customize the calendar view in a way that would allow us, for example, to track events (records) that are occurring simultaneously across various locations (dropdown field). Kind of like how you can see various Google Calendars side-by-side (which was the workaround we used this year via Zapier).  A more specific breakdown of what we're looking to do is as follows: - The ability to create sections within the calendar view based on a dropdown field within the Table. Since we're hosting events across various venues throughout the day, it's vital that we see every event side-by-side, split up by venue to ensure there's no overlap. - When choosing to add other date fields to pull from, it'd be great to be able to customize what information goes into those additional date fields instead of AirTable just expanding the main record. Example: Each event (record) has an introduction, Q&A, and turnaround time. If there was a way to have the calendar show those different start/end times separately, and if we could choose what areas from that record are highlighted, that would be ideal. ... View more

What is the proposed idea/solution? The proposal is to abolish the fees for Interface-only commentor level. Actually, a commentor is a viewer with the possibility to comment, nothing beyond that. No edits, no creation,  no management, etc.   How does is solve the user problems? It would change how companies (like my agency) can communicate with their clients (specifically those who are not active on a daily basis) or external partners over e.g. the workflow, reducing e-mails or calls. Clients (free of fees) can add records to a base via forms and can read them on Interface, but there is no chance to leave a comment. ... View more

We have an interface for our project management Airtable base, which shows project data filtered by a record list. As our base grows, the page has grown with it and is quite long, split into useful sections. I would like a way to hyperlink to different sections within the interface, like using div IDs and # hyperlinks in html.  This could tie in to a standard button, as currently used for navigation to external URLs.  ... View more

What is the proposed idea/solution? Providing Interface designers with the ability to allow/disallow the visibility of the field "i" tooltip inside Interfaces. How does is solve the user problems? Currently, we are using text blocks in the UI to explain certain field purposes or possible pitfalls of user selections. You can really clean up an interface and reduce user support questions by providing them with the ability to get further information before making a choice at the exact moment in their workflow that it is appropriate. Blocks of text mean to help a user perform functions really make the entire interface too cluttered to use for experienced users. Some users don't use the system very often so they usually completely forget and need this help but. Maintaining two interfaces with different levels of "Info Help" is not a viable option. From an administration standpoint, this allows for already existing documentation to now serve both database designers and end users at the same time. Future leaning thinking also implies that there could be two fields for "Description" - each with a different set of permissions so that admins can leave themselves complex backend notes for themselves and their teams yet provide more simple descriptions for interface front end users. How was this validated? N/A Who is the target audience? Anyone designing interfaces for themselves or others ... View more