Explore  

This article discusses functionality that is included in the Enterprise+ plan. Please contact us if you would like a live demo or would like to try using it in your account.

Aha! Roadmaps | Custom tables (Enterprise+)

There are hundreds of ways you can customize Aha! Roadmaps to match how your team works. Some teams may wish to go beyond custom statuses, fields or terminology and add their own custom extension to the Aha! Roadmaps data model. Custom tables enable exactly this.

A custom table for Strategic Partners

By managing this information directly in Aha! Roadmaps, you can make better prioritization decisions and share the most important information related to your plans and roadmaps. For example, you could make a custom table to manage a central list of key strategic customers. In addition, markets or opportunities can be centrally located and visible across your organization.

What you track with custom tables is completely flexible and up to you — in all cases, you can then easily link what is being tracked to your initiatives, features, and ideas for a single view into roadmap impact.

Click any of the following links to skip ahead:

How it works

A custom table is a collection of records organized in a table with data defined by custom fields. The information can be managed within Aha! Roadmaps and can also be programmatically imported and kept up-to-date through our API.

Administrators with customization permissions on the Enterprise+ plan can create and configure custom tables by following these steps:

  1. Navigate to Settings ⚙️ Account Custom tables and click Create custom table.

  2. You can create your custom table from scratch or begin with an example table and modify it as necessary. The examples you will see are for common use cases, including datasets related to customers, markets, opportunities, partners, or release history. The example tables create a set of relevant custom fields. If you use an example table and you'd like to link the custom table to your existing Aha! Roadmaps records, you will still need to set up a relationship custom field. See step 4.

  3. Add and modify custom fields by clicking the Add custom field option or click on the custom field name to modify the field. Note: The value in the first field will be used as the identifying name for the row's record when it appears in Aha! Roadmaps.

  4. Link your custom table to existing data via three custom field types: one-to-many relationships, many-to-one relationships, and many-to-many relationship. One-to-many relationship fields display the whole custom table on a record, and allow you to edit the custom table from that record. Many-to-many and many-to-one relationship fields let you link records to custom table records.

Don't forget to add your one-to-many or many-to-many custom fields to a record layout!

Notes:

  • If you add a one-to-many relationship to a custom layout, it will appear in the record layout as its own tab, rather than a field within a tab.

  • After you have created a custom table, a new Custom tables option will appear in your workspace settings.

Custom table account-level settings

Owners and contributors on the Enterprise+ plan can add records to any custom table in the account. Custom table records are associated with a workspace or workspace line. They can be viewed and edited from a given workspace or workspace line in your workspace settings. Each tab represents a table with data in the selected workspace.

You can edit many custom table records at the same time using bulk edit.

Custom tables need at least one record before they will appear in your workspace settings. To add the first record to a custom table within a workspace, click the + icon and select the custom table from the Add custom table dropdown. Once the first record has been added, the records can be accessed and edited through the new corresponding tab.

Screen to add a new custom table

Top

One-to-many relationship

The one-to-many relationship embeds a custom table on another record as a tab in its detail and drawer views. You can add, edit or delete information on the custom table from the record (or from the custom table, of course). The benefit of the one-to-many relationship field is that you can see the whole custom table at once — and have full context when you update information on it.

Note: If you want to use a spreadsheet-like table in your records, you may need a custom table, or you might benefit from a custom worksheet. You can use custom worksheets to perform calculations on data using custom equations and a variety of field identifiers.

For example, say that your team has trouble shipping releases on time. You could use a custom table to track releases in your account that have shipped past their expected release date. Add fields to track the expected release date, actual release date, and any comments on the slip.

If you add this table as a one-to-many field for releases, then the details and drawer views for all releases will contain the custom table which can be easily updated as needed to reflect changes to the release schedule.

If you add a one-to-many relationship to a custom layout or an advanced custom layout, it will appear in the record layout as its own tab, rather than a field within a tab.

Release linking to a custom table with a one-to-many relationship field

Top

Many-to-many relationships

The many-to-many relationship custom field functions similar to a predefined-tag field. It allows you to associate multiple records from a custom table to your Aha! Roadmaps records. For example, associating customers with a feature.

Feature linked to a custom table with a many-to-many relationship

What makes the custom table especially powerful is that by clicking on the tag, you can open up the drawer view for that specific custom table record, allowing you to view key information for the underlying record.

Custom table record drawer view in front of a feature

When adding a many-to-many field, you can specify which custom table records are available for selection from the Record visibility setting on the custom field.

  • Entire account: Displays all records in the account. While all records are available for selection, the user will only see those available for their user permissions.

  • Workspace and workspace lines only: Displays only records that are in the current workspace and those inherited by its workspace line(s).

Create many-to-many custom table relationship field for features

Top

Many-to-one-relationships

Like many-to-many relationships, many-to-one relationship custom fields function similar to a predefined-tag field. However, they allow you to associate only one record from a custom table to your Aha! Roadmaps records.

Feature linked to custom table with a many-to-one field

This is a useful constraint if you want to be sure that each record associated with your custom table is associated with only one custom table record. Just like in many-to-many relationship fields, you can click the one custom table record to open up its drawer view, and you can adjust a custom table's Record visibility setting on the custom field.

  • Entire account: Displays all records in the account. While all records are available for selection, the user will only see those available for their user permissions.

  • Workspace and workspace lines only: Displays only records that are in the current workspace and those inherited by its workspace line(s).

Top

Report on and search for custom tables

Custom tables allow you to visually bring data together. As with all Aha! Roadmaps data, the data in a custom table is reportable. To view your custom table as a list report, which opens it up to the ability to add filters, sorting, and other data, click the More options menu on the righthand side of your custom table, then click View as list report.

Beyond that option, you can generate lists, pivot tables, charts, and timelines from your new custom table, and reference custom table records in custom worksheets. You can also search for custom table records using Aha! Roadmaps search.

Note: Custom table relationship fields are not sortable fields.

Column chart showing feature count by customer based on custom table

Top

If you get stuck, please reach out to our Customer Success team. Our team is made up entirely of product experts and responds fast.

Suite overview
Aha! Roadmaps
    Roadmaps
      Integrations
      Aha! Ideas
      Aha! Whiteboards
      Aha! Develop
      Release notes