Feature Ideas

Trending
  1. Non-primitive sub-inputs

    Allow component inputs to accept custom (non-primitive) types as sub-inputs, so that developers can define reusable complex types and use non-primitive inputs - such as measure selectors - within them. Currently, sub-inputs are limited to primitive values (strings, numbers, booleans). This forces developers to flatten what should be structured, grouped inputs into explicit top-level fields as a workaround, rather than modelling them as arrays of a custom type with rich sub-inputs.

    Ella Cullen

    0

  2. Be able to pin components to the top of the screen such that when a user scrolls down the filters stay visible

    Allows for things like filter updates while viewing graphs near the bottom of a dashboard without having to scroll back to the top, change the filter, and then scroll back to your graph of interest.

    Michael H

    0

  3. A Duplicate button on dashboard widgets

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

    Nickolas L

    5

  4. Show/hide parts of a dashboard based on a variable

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

    Tom G

    2

  5. Containers for components

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

    Ella Cullen

    7

  6. Support for nested AND and OR logic in dataset filters

    Currently dataset filters all use simple AND across each filter. It is, however, common that you might want to use OR instead, or a nesting thereof.

    Tom G

    3

  7. String interpolation: ability to use a variable in text inputs

    It would be nice to have a variable, e.g. granularity, populate a text input, such as a chart title, so that for example a chart title can be 'Sales by {granularity variable}' and update based on the end users filters

    Ella Cullen

    1

  8. Be able to match component sizing in the canvas

    It would be super helpful to be able to have multiple components be the exact same height/width, especially if this could be set easily in the canvas.

    Ella Cullen

    0

  9. Geo heatmap chart

    A map, including zoom capabilities, that uses colour intensity to show the concentration or magnitude of data across geographic areas. Hotter colours (e.g. red) indicate higher values, cooler colours (e.g. blue) indicate lower values. e.g. https://www.highcharts.com/docs/maps/geoheatmap-series

    Harry

    0

  10. Copy or clone an Embeddable from one workspace to another

    In some cases you might want to have multiple workspaces to allow for connecting to different cube instances (for example). In order to allow for easy testing of dashboard / Embeddable configuration across different instances, it would be helpful to be able to clone a dashboard from one workspace to another

    Ella Cullen

    1

  11. Drag-to-select on dimension axis

    This is a really nice feature to enable end-users to zoom in on a specific period (for example)

    Ella Cullen

    0

  12. Have a search/filter in table columns

    This would enable end users to search/filter the table easily

    Ella Cullen

    1

  13. Don't show 0.5 increments if the numbers displayed aren't FLOAT

    When you go under a certain number, chartjs automatically shows ' 0.5' increments on charts, which don't really make sense if the measure data being shown isn't type FLOAT

    Ella Cullen

    0

  14. Custom Canvas Template Search Function

    I have a lot of templates available to users, and it's only going to grow! I'd like them to be able to search through the templates by name or by what data is being displayed.

    Sophia

    0

  15. Show where variables are being used when a variable delete is blocked by usage

    A change in how we wanted the dashboard to function necessitated some variable cleanup and it was used in 12 places, I easily found 11 of them and the 12th was filtering the dataset itself and it took an embarrassingly long amount of time to find. Would be great to have an easier way of identifying where the variable you are trying to delete is used. Would also be good to be able to quickly double check which charts a variable is applied to for things like full dashboard date filters or something to ensure no components were missed.

    Michael H

    0