🚨New Feature Alert! | Implement Pivot Tables in Airtable Dashboard

Поделиться
HTML-код
  • Опубликовано: 18 окт 2024

Комментарии • 13

  • @GarethPronovost
    @GarethPronovost  6 месяцев назад

    Get our *FREE AIRTABLE CRASH COURSE* here 👉👉 garethpronovost.com/airtable-crash-course ⚡⚡
    Follow along in Airtable here 😍😍 airtable.com/invite/r/v0eI3ASY 🤓🤓

  • @steveruqus2680
    @steveruqus2680 6 месяцев назад

    Excellent job as always.

  • @Londya
    @Londya 5 месяцев назад

    Hi Gareth, thanks for this tutorial! Really cleared it up for me. Can you do a full tutorial for the new dashboards? Like a breakdown of all the chart types and any tips for designing.

  • @akaalx
    @akaalx 6 месяцев назад

    How do you chart it?

    • @GarethPronovost
      @GarethPronovost  6 месяцев назад

      Do you mean how to create a chart in an interface?

  • @godynnel7680
    @godynnel7680 6 месяцев назад

    Wow, that seems like a big feature - only at start of vidoe though so 🍿

  • @XAE_A_Xii
    @XAE_A_Xii 6 месяцев назад

    I can’t wait when AT brings the feature where you can transpose the data. The horizontal layout is not great, you can display a lot more data in vertical format

    • @GarethPronovost
      @GarethPronovost  6 месяцев назад

      Curious why you'd need data transposed in Airtable. Records and fields are pretty specific and I'm not sure how swapping rows and columns changes things?

    • @XAE_A_Xii
      @XAE_A_Xii 6 месяцев назад +1

      @@GarethPronovost you can fit more data in a single screen, especially when you work with numbers. Imagine you have a long header such as £Delivered UK cost/unit and just few digit numbers below. And when you have a lot of such columns you will see you are wasting a lot of space just for the sake of being able to read the headers or part of them. I know AT is not exactly for finance but I spend half day everyday updating it, so I know this issue very well. I don’t use interfaces because in my job I tend to update multiple rows simultaneously. Another suggestion is to split the view into two parts- one half is horizontal as usual which would contain non-repetitive data, and the other half would summarise common data within the group of data. For example, you have a list of products each having its own price, SKU, barcode etc, but at the same time since they all belong to one particular group of products they all have the same logistical details: unit per pallet, per truck, per container and so on, some direct costs (royalties %, freight etc).

  • @blackshard641
    @blackshard641 6 месяцев назад +2

    Interfaces will continue to be useless until they can be shared publicly.