Feature Ideas

It's currently possible to make dashboards live programmatically via the API (https://docs.embeddable.com/deployment/versions#two-control-models), but this uses a different flow to the in-platform "publish" flow. Some teams would like to be able to combine the two (i.e. use in-platform "publish" flow sometimes, but also publish via API). This ticket is about achieving this by providing an API that allows you to do the "publish" flow via API.

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

End users can download their dashboard as a PDF

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

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

Like this (https://restpack.io/html2pdf) but specifically for your embeddable dashboards

Easily undo or redo changes made in the no-code builder.

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.

We're building a set of dashboards for customers to get insights into their Embeddables, including information on unique viewers, query performance, dashboard performance, error messages, and more.

Sometimes you don't want loadData to request data from your database until a certain condition has been met, e.g. user has chosen a filter or date range.

e.g. the ability to use Excel-like logic (if-else, maths, etc.) to write custom expressions using measures and dimensions, directly in the builder (without needing to update your model). Currently you need to manually define a new measure or dimension in the model (e.g. "{active_users} * 100 / {total_users}") to achieve this.

When the screen size changes, components dynamically re-size, but it would be useful to be able to control how this happens

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

When a dataset is pre-selected in a template component, filter/sort/limit options become unavailable after the template is used. If the dataset is left unselected, filtering is available - but this adds an unnecessary step for end users. The request is to support both: pre-selecting a dataset in the template AND allowing users to filter on it post-use.

This would be a cool addition to the out-of-the-box charts