Showing ideas with label Extensions.
Show all ideas
Status:
New Ideas
Submitted on
‎Dec 09, 2024
01:52 AM
Submitted by
Paul_Thompson
on
‎Dec 09, 2024
01:52 AM

We need a 'Conditional Select' type field to add to forms. This type of single select and multi select question would conditionally disable and 'grey-out' specific options in select questions on forms. It doesn't seem currently possible to do this. There would be many use cases for this. My particular one is that I have a form for view only users to update certain fields in a database for a not for profit or charity music school recording students and musical instruments loaned to them. We need to prevent students resigning but not handing instruments back. The first single select question on the form is "What do you want to do?" which hides/shows various fields on the same form. One of the options is to resign a student. If that student is still holding an instrument, (ie. {instrument ID} is not blank) It should not be selectable, but should still be visible, greyed out so that the user can see they are in the right place and its clear they cannot select that option. An important feature of the proposed conditional select field would be the option to include a warning message when the disabled option is clicked or hovered over, which should allow the inclusion of variables from the source field causing the restriction. ie. in my use case, I would want to say, "{First name} cannot be resigned at this time because records show they are still holding the instrument {Instrument ID}. I think this feature would be of great benefit to a lot of Airtable users.
... View more
Status:
New Ideas
Submitted on
‎Sep 20, 2024
12:52 PM
Submitted by
Jasonl2l
on
‎Sep 20, 2024
12:52 PM

I think a key missing feature is the ability to embed items into an interface. I think this could take one of two (or both) forms. 1. A field that functions kind of like a "document" field. You insert an embed link. When viewed in a base, or in a grid/list view, it just shows as a preview - But when viewed in a record details pane - it translates to a custom sizable-embedded page. Each record's embedded view is based on the link in the field - just like the Button field type. 2. A "hard-coded" form - kind of like the difference between the "button field type" and the buttons you can set up in an interface. In the from-scratch interface builder - there would be a new element type called "Embed" where you could manual populate to with whatever embedded link needed. For example a google doc - or a news feed, etc. This by itself would accomplish half of the ideas that users have been putting forward for new automation triggers and integrations.
... View more
Status:
New Ideas
Submitted on
‎Sep 19, 2024
01:03 PM
Submitted by
Mike_AutomaticN
on
‎Sep 19, 2024
01:03 PM

What is the proposed idea/solution? Base Schema extension... on steroids 💊!! The existing base schema extension is ok, but could be way better for documenting the base. Simple updates/requirements: 1. Allow for multiple slides/pages where different views/arrangements of the schema can be shown 2. Hide certain tables (when you want to show or explain one specific workflow) 3. Hide certain fields 4. Include table descriptions 5. Include field descriptions 6. Allow for a Header for each slide 5. Allow for text notes within each slide. How does is solve the user problems? Current base schema is good for understanding and visualizing, but not for documenting. Only a few additional features are needed. The whole base would be documented in one same place (extension), going through different workflows and structures in a neat and organized way. It would recycle already existing table and field descriptions. Who is the target audience? All Airtable users with complex bases!
... View more
Status:
New Ideas
Submitted on
‎Aug 09, 2024
10:45 AM
Submitted by
Kiersten_Kollin
on
‎Aug 09, 2024
10:45 AM

Create a toggle button for multi and single select fields to not allow new select options to be added by an Editor that creates records. We would like to allow Editors the ability to add records but not add rogue field options, which is hurting our data that we want to track. We do not want to grant them any higher access to be a Collaborator. Current state, we are spending a lot of time to continually re-train the users to not add in rogue select options. This toggle button option should carry through the CSV Import Extension so no button appears for users to try and add in missing options.
... View more
Status:
New Ideas
Submitted on
‎Jul 26, 2024
08:18 AM
Submitted by
Mark_Balsam
on
‎Jul 26, 2024
08:18 AM

What is the proposed idea/solution? True emailing and calling functionality. The ability to send and receive emails and make and receive calls within airtable and have them log to the record or even multiple records. Preferably the user would be able to choose from popular third party email and phone providers that would integrate in. How does is solve the user problems? To my mind, with this feature, airtable now becomes a real alternative to CRM systems, helpdesk/ticketing systems, etc. How was this validated? ... Who is the target audience? Really anyone using airtable. The most popular CRMs and other systems are starting to feel old and tired. People WANT to use airtable for more and more things, but until there are true communication features built in, it's hard to do so.
... View more
Status:
New Ideas
Submitted on
‎Jul 10, 2024
05:33 AM
Submitted by
Hill672
on
‎Jul 10, 2024
05:33 AM

What is the proposed idea/solution? Add the ability to share the Matrix App Extension output How does is solve the user problems? We've used the Matrix Apps ability to arrange records on a 2D grid to create a value versus effort grid and the output is perfect for our requirements. However, there is currently no way to share the output other than via screen capture. The proposed solution would allow us to share the live grid with our user base so that they can see our approach to prioritisation. How was this validated? user request Who is the target audience? Product Owners
... View more
Status:
New Ideas
Submitted on
‎Jun 24, 2024
07:20 PM
Submitted by
Troy1
on
‎Jun 24, 2024
07:20 PM

My organization has developed an extension using the block APIs to perform repetitive tasks and run analytics on our bases. This has been working great, but the issue is that our workflow involves creating one base per project. With the current block APIs, this requires the developers in our organization to go into each new base, start the extension creation process to retrieve the blockId, then run some command to add the new remote, and finally deploy the extension to the new base. As we expand our usage of Airtable and create new bases, this is quickly becoming unmanageable, as each base requires the developers to run these commands. My idea is to allow extensions to be released at the organization level. Then, when a user creates a new base, they can go over to add an extension, see all the extensions owned by their organization, and add the extension to the new base they have created.
... View more
Status:
New Ideas
Submitted on
‎Jun 21, 2024
11:11 AM
Submitted by
Jason_Knighten1
on
‎Jun 21, 2024
11:11 AM

To whom it may concern, An enhancement suggestion from Kalypso: Improve functionality for Base Schema extension (See screen shot for Kalypso base configuration). Currently with our base, it is challenging to follow highlighted relationship mapping lines even with the filter capability Enhancements might include: Right click on dependency line to see details of the dependency in a pop up (What dependency type, table and field names on each side of the dependency) Use different colors to represent different dependency types Ability to separate the tables with either a drag drop or pre-configured distance options Expected Benefits: Improve the ability to use the base schema for its intended use to visualize table/field relationships. Reference screenshot Please consider adding this capability. Regards, Jason Knighten
... View more
Status:
New Ideas
Submitted on
‎Jun 21, 2024
08:27 AM
Submitted by
Jason_Knighten1
on
‎Jun 21, 2024
08:27 AM

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
Status:
New Ideas
Submitted on
‎Apr 30, 2024
09:33 AM
Submitted by
Michael_Andrew
on
‎Apr 30, 2024
09:33 AM

What is the proposed idea/solution? There needs to be 'overall' more chart functions, but a very important one for us is the ability to 'split'. For example, an item may have a field that is an array (multiple select, or linked records). We want to count the items individually, so need a 'split' function that is common in other BI platforms (Tableau, PowerBI) to allow for charting of counts of array items. How does is solve the user problems? Currently, charts would count items by the specific array (e.g. China, United States would be one item, rather than China 1, USA 1).
... View more