Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add an option to customise the file name for widget data export #10809

Open
dmohns opened this issue May 16, 2024 · 0 comments
Open

Add an option to customise the file name for widget data export #10809

dmohns opened this issue May 16, 2024 · 0 comments
Assignees
Labels

Comments

@dmohns
Copy link

dmohns commented May 16, 2024

Is your feature request related to a problem? Please describe.

In my use-case I want to provide customers the possibility to export device-level data in CSV. I created a dedicated dashboard with a single table widget which users can use to export data for a single device.

It is not uncommon for users to export device data for 10 or more devices. Which will result in a lot of files in their download folder

Sensor Telemetry Data.csv
Sensor Telemetry Data (1).csv
...
Sensor Telemetry Data (10).csv

It can be tedious to identify which CSV belongs to which sensor.

In an ideal world the downloaded CSV would contain the devices ID or name.

Describe the solution you'd like

For every widget that supports data export, in the Card Buttons setting view, where we can enable [x] Enable Data Export: Add an optional text field which customised the Data Export filename (without extension). This should be defaulting to the current value for every widget.

This should also allow templating for example export_${entityName}.

Describe alternatives you've considered

Only alternative would be to clone the widget and create a custom implementation where I set the Data Export filename as required.

Additional context

N/A


Disclaimer

We appreciate your contribution whether it is a bug report, feature request, or pull request with improvement (hopefully). Please comply with the Community ethics policy), and do not expect us to answer your requests immediately. Also, do not treat GitHub issues as a support channel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants