Feature Ideas

Cube supports setting total to true (here) in order to have it return the total row count (here). In Embeddable we set this to false, as setting it to true can be very detrimental to query performance. A workaround, for pagination in Embeddable, is to use a second loadData request to request the row count. This roadmap ticket is about exposing the option to set total to true and return it in the loadData response, so that you don't need a separate loadData request.

It would be great if Embeddable supported the total attribute that the REST api of cube supports as it adds a total amount of records to the query result.

Make it easier for Embeddable builders to organise their Embeddables using folders.

Ability to invite your team to your workspace via UI

It would be great to have this kind of control on the Embeddable canvas

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.

Enable builders to publish to environments such as QA, Test before publishing to Prod.

This will allow you to dynamically control which dimension or measure to segment or aggregate by. E.g. you could have a dropdown containing a list of dimensions or measures, and then when users switch to another dimension or measure, all the charts update to show that dimension or measure.

End users can download their dashboard as a PDF

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

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

It would be useful to be able to clone a dashboard from the live workspace to local dev preview so that it could be worked on locally

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.

Something to ease a component prop migration, or to create a template in case we go into the hundreds of dashboards. E.g. a basic import/export JSON endpoint to configure an Embeddable