Feature Ideas

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.

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

Some of our partners complain that they have to constantly change dates every time they change one tab from another on our Embeddable reports. I have tried to use the tab solution Ella shared with me, but that right now is a lot of custom management. Ideally, we could group Embeddables that could share the same date filter. That could even be useful to create "folders" on the Embeddable builder page.

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

An API for retrieving the metadata for a published Embeddable dashboard: The canvas layout (position and size of each widget)The component values (input values and types for each of the component inputs)etc. E.g. GET https://api.embeddable.com/api/v1/embeddables/{embeddableId}

When you change a model (add/remove/change a dimension/measure/join/etc.) this may cause certain Embeddables to break (component inputs / interations, dataset models, sorts and filters, etc.). This idea is about having some kind of report that tells you exactly which Embeddables have been (or would be) broken by your model changes, so you can quickly track them down and fix them.

Ability to monitor your live Embeddable dashboards in your existing monitoring tools (please comment below which tools you'd want us to support).

It would be really helpful to have a guide for all the possible error codes, to make it easier to track down the root of a particular issue.

Sometimes the choices that users make in earlier parts of a component form make other inputs relevant/irrelevant. This ticket is about allowing the visibility of certain inputs be dependent on the value of other inputs.

When building custom components, we should be able to support Via the .emb file Example use case, allowing a chart to have multiple series, but each series can have it's own style (bar, line, etc)

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

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