Showing ideas with label templates.
Show all ideas
Submitted on
Aug 20, 2019
08:54 AM
Submitted by
Ralston_Vaz
on
Aug 20, 2019
08:54 AM

Is there a way to make a template for a type of record that will be used multiple times for new instances of the same kind? For example, I follow a seven-step process when designing logos. I have a base tracking projects using records that include details like tasks to complete. The seven steps I follow are captured as tasks for each project record. I’m finding that I’d have to recreate the list tasks for every logo design project. It’s a lot of repetitious work. If there’s a way to make a template of a logo design record to start with and customize for each new project instance without lingering link issues that would be fantastic! Is that possible in Airtable without any add-on app? If not, can it be made possible?
... View more
Status:
New Ideas
Submitted on
Feb 11, 2025
10:58 AM
Submitted by
alwayscur1ous
on
Feb 11, 2025
10:58 AM

What is the proposed idea/solution? Today the only way to add buffers between dependent project tasks (i.e. tasks where one task is a predecessor to the other) is to view the project in timeline view. You have to click on the dependency and manually set the buffer. Many of my projects depending on adding a delay to the start of a dependent task after its predecessor is completed and having to hand add buffers in timeline view to support this is not sustainable. How does this solve the user problems? This allows to a scalable approach to project creations via record templates where users need to add a delay between the completion of one task and the start of the next task dependent task (i.e. this task has a predecessor defined) without doing a ton of manual work in timeline views.
... View more
Status:
New Ideas
Submitted on
Dec 11, 2024
01:08 PM
Submitted by
Chais_Meyer
on
Dec 11, 2024
01:08 PM

Proposed Idea/Solution: The idea is to introduce a “Default Column Order Template” in Airtable. This template would allow users to define a consistent column order that automatically propagates to any views linked to the template. For example: •If View #1 and View #5 could both reference the same “Default Column Order Template” (e.g., “Template: Customer Service Data”), any changes made to the column order in the template would dynamically apply to both views, maintaining consistency. •While linked views would share the column order, they could still independently choose to show or hide specific fields/columns, giving users flexibility while ensuring a uniform structure. This feature would save time, enhance collaboration, and reduce errors caused by inconsistent column arrangements across multiple views. How Does It Solve User Problems? This feature addresses several challenges: 1.Efficiency in Multi-View Management: Users working with multiple views often need a consistent column order to streamline workflows. Manually maintaining the same column order across multiple views is time-consuming and prone to errors. A default column order template would ensure consistency across views with minimal effort. 2.Team Collaboration: In collaborative environments, different team members might use different views of the same data. Having a consistent column order ensures everyone is aligned, reducing confusion and making it easier to locate fields. 3.Improved User Experience: For projects involving multiple teams (e.g., customer service, marketing, and analytics), a unified column order reduces onboarding time for new team members and enhances data usability. 4.Dynamic Data Adjustments: As fields are added, removed, or reordered in the template, linked views dynamically reflect those changes. This ensures up-to-date and organized data without requiring manual updates in every individual view. How Was This Validated? While this request arises from a practical need observed in real-world workflows, its benefits have been implicitly validated through user behaviors and existing challenges: 1.User Feedback Patterns: Many Airtable users express frustrations in forums and support requests about the manual effort required to maintain consistent views. This feature would directly address such feedback. 2.Analogous Features in Other Platforms: Systems like spreadsheet templates or CMS tools often offer shared configurations for layout or structure. These serve as precedent for the efficiency and utility of such a feature. 3.Internal Testing Opportunities: Airtable could validate this feature through beta testing or user surveys, targeting teams or users managing complex bases with numerous views. Additional Use Cases: 1.Customer Relationship Management (CRM): A sales team and customer service team might use different views of the same customer data. Maintaining a consistent column order ensures smooth transitions between teams without data disorientation. If 50% of their views need to be different, for their CS team as an example, then that team would use their own template! 2.Project Management: A project manager might create views for “High-Level Overview” and “Detailed Task Tracking,” where consistency in column order aids in quickly understanding data context. 3.Event Planning: An event planning team could have separate views for “Guest List,” “Catering,” and “Budget,” but benefit from a unified column order to avoid confusion when cross-referencing data. 4.Analytics & Reporting: Analysts working with multiple dashboards can maintain uniform field arrangements, making it easier to compare and combine data. This feature would be a game-changer for users managing multiple views and collaborating across teams, ensuring Airtable continues to be a leader in dynamic data management.
... View more
Status:
New Ideas
Submitted on
Jun 21, 2024
08:24 AM
Submitted by
Jason_Knighten1
on
Jun 21, 2024
08:24 AM

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
Status:
New Ideas
Submitted on
Feb 14, 2024
01:38 PM
Submitted by
nbsheriff61
on
Feb 14, 2024
01:38 PM

According to the feature documentation for Record Templates, there is a default behavior by field type when applying a template to an existing record, as follows: Empty non-array type fields are filled according to the template's configuration Array-type fields are always appended to and deduplicated Non-empty, non-array type fields are ignored Computed field types cannot be directly modified by templates I suggest allowing these behaviors to be modified per template, through a similar screen as relative date settings can be. As an example, Single Select fields fall in the 'non-empty, non-array' category, but I often need to change one of these fields (e.g. Status) along with other changes to the target record. Assuming the categories must stay the same, the following options would be very helpful: Empty, Non-Array: Ignore or Overwrite Array: Ignore, Overwrite or Append Non-Empty, Non-Array: Ignore or Overwrite
... View more
Status:
New Ideas
Submitted on
Dec 01, 2023
12:50 PM
Submitted by
flyinsolo
on
Dec 01, 2023
12:50 PM

Added this as a comment to the Record Templates announcement but also wanted to add a new thread. I'm trying to build out a new workflow where team members can create new records in one table via a Linked Record field in a different table. When you click the " + Create a new record" option at the bottom of the Link Record dialog, you get the new record as an expanded record showing the fields visible in the very top view of the table. I'd love for the top right options menu (below) to have an "Apply template" option somewhere so I can more seamlessly create new records using existing templates, rather than having to click out of the expanded view, navigate to the table the new record is located in, and apply the template there. A little paint bucket between the link and comment icons... pretty please... Not make-or-break, as it's ultimately a small thing, but it would make for a much more seamless experience overall, imo. Thanks!
... View more
Submitted on
May 18, 2020
09:04 PM
Submitted by
Ellen_DeGennaro
on
May 18, 2020
09:04 PM

These days I think a lot of people would find it very useful to have a better way of wrapping their heads around how to maintain social distancing in the workplace across many shifts, but with varied staff each with different responsibilities. I think Airtable is ideal for this. I made a sample with a fictional biotech company here, but there’s many many potential applications. Can we make this happen?
... View more