Feature Ideas

Drilldowns are super helpful for end users, so being able to add them within the no-code builder is really important - e.g. by opening a sub-embeddable via a modal.

Sometimes a part of a dashboard only makes sense to show once the user has selected an input.

To make building dashboards in the no-code builder easier, we'll introduce the concept of 'containers' to layout components on the canvas

We will be introducing "filters" as a variable type to dynamically apply dataset filters.

It would be great if it was possible to define the breakpoints in the Embeddable canvas when it's in use on different size screens, instead of just having the default ones.

Queries against your database (especially warehouses like BigQuery and Snowflake) are expensive, and so, if a dashboard can perform a single query to get the data needed to populate multiple charts, this would significantly reduce the cost of a dashboard. Note: This is different to pre-aggregations, which load data pre-emptively and keep them refreshed. This is instead about requesting data from the database on-demand, but reducing the number of necessary queries to do so.

Wouldn't it be amazing if there was a copy/clone button close to the Edit and Delete ones 🥺

Download an Embeddable as PNG/image

It would be useful to be able to have tabbed Embeddables so that you don't need to create tabs within your own application, and you can use the same datasets / configurations across the tabbed Embeddables.

It would be useful to be able to rotate API key for additional security.

Docs: https://cube.dev/docs/reference/data-model/segments

Once embedded, it's not possible to see the query being executed. This would be useful to have access to.

Embeddable already allows you to override variables in your Embeddable, dynamically, when Embedding in your app. Testing this in the builder, however, is a little manual right now. This feature will allow you to define set variables for each client-context, and switch between them as you switch client context in the builder.

End users can download their dashboard as a PDF

Currently Embeddable uses UTC by default (e.g. when aggregating results by day / week / etc.). We plan to support supplying a timezone, per dashboard session, so each user can see the results in the timezone that makes sense for them. This will also involve making the caching layer timezone-aware.