Planhat's data tables allow you to manage your customer data model with the ease of a spreadsheet (in-line editing, simple add/remove of columns, updating column/field settings) with the power of data warehouse (you're actually managing a database sourced from multiple systems).

But with a lot of data comes a need for visual structure to segment and understand it better. The "Grouped View" in data tables is an effective way of doing so, which you can combine with sorting within each group to identify priorities.

  • Group Companies by Owner, or by Phase, or Plan to get a rich overview of data

  • Group Licenses by Status to see what you need to what action on, or Group by Company and sort by End Date within each group if you are multi-product

  • Group Playbooks/Workflows by Template (eg, Onboarding Playbook) to understand what needs attention in each part of the lifecycle

  • Group Opportunities by Stage to know where to spend more time

  • Group Issues/Ticket by Category, or by Product module

Or some more specific ones that our team members found in the first 10min:

  • For my private filter of companies, include companies where I'm both Owner and Co-owner, and then Group by Owner > produces a single overview of all accounts I'm involved in, but split by whoever I'm partnering with

  • Group our Issues/tickets by Sprint, to create an easy overview of all currently active sprints the product team is managing in Planhat (yes, we do our PM in Planhat!)

As you can see, the recurring pattern is that a Grouped View helps you take action from a high vantage point - it lets you group your data like a Kanban view, but with the added richness of seeing multiple data points, sorting within each group, etc.

To implement it, press the Manage Table in top-right of a data table and add a Grouped View. You can also add this as a default view for a Filtered view.

Some important notes:

  • This is not yet available in Live Data Tables in Pages (coming soon)

  • You can Group by any property except for:

    • Same-object IDs or Names (so eg, on companies we don't need to be able to group on company ID)

    • Fields of type multipicklist

    • Fields of type rich text

    • Fields of type team members (note: you can still have "team member", but not when multiple)

    • Fields of type end users (note: you can still have "end user", but not when multiple)

    • Any revenue fields, like ARR on company object

    • "Relevance" property on enduser object

    • Fields containing the string "[ ]" - this is purely a technical thing that will be updated down the line

We're very excited about the potential for Grouped View in helping users take action on big data sets, so we will continue to invest in making it even more flexible and usable across the entire app. As always, please share feedback!

Did this answer your question?