Feature Ideas

Ability to leverage a highly formatted Microsoft Word template with tags that match to data stored in a dataset and have the export capability to create and export multiple pre-filled templates.

Add the ability to add a trend line to a chart the way that Microsoft Excel provides.

Currently, you can set a static name for the attachment that goes out via scheduled email. It would be nice to have dynamic values such as a date to append to a file name such as, report20-12-09.pdf.

Right now number formatting only applies to the main KPI value and not the goal. Provide the ability to set the number format of the goal value in the KPI.

Instead of having to export data from DashboardFox into Excel, it would be nice to have an Add-in which can directly connect and pull and refresh data into an Excel sheet. This could also apply to Google Sheets.

Allow the arranging of saved fields in the same way you can re-organize and order your favorited dashboards.

Currently only admins are able to reset a users password if they forget it. Enable a forgotten password feature for agents and builders.

Currently many of the error messages that are returned when a report fails are errors provided directly from the database. This means that most of the messages are not extremely user friendly and don't provide easy to understand information on the issue with the report or how to solve it. This idea is to revamp the error reporting to provide more user friendly messages.

Allow users that know how to write SQL queries or already have SQL queries generated to be able to leverage those in the DashboardFox report building process. Please leave feedback on how you would use this feature and where you would want it. For example: Creation of a DashboardFox App dynamically from a SQL query. This would limit access to App Builder level users and continue to leverage the DashboardFox App which is the hub of all security and Composer Access. Allow Composers to create reports directly from SQL queries. This would potentially by-pass DashboardFox security and allow anyone with builder access to run any query they wanted, Feedback on your desire and use case for this needed.

Currently the composer has full control of what report data can be shared as a Guest View or Public View Document. This feature is to include the Guest View or anonymous user as a reserved user type so that it can have Data Security policies attached. So regardless of what the Composer creates, the organization can set a policy on what data limits are.

Currently, when you union multiple documents there is no way to set the order and the only way to do it is to delete and re-add the documents. Allow the ability to arrange the documents, so they display in the desired order.

Currently, the dropdown list you get when you select equal on a date provides a long list of date calculations, but it's not possible to add/remove/update them and not all are applicable to all organizations. Include a way to configure and organize those without assistance.

Currently, you have to edit each folder and document when you need to add a new security group (unless you programmatically use the API). Add a method to the interface to select multiple reports to bulk update groups and an option at the folder level to apply to all reports and subfolders within.

Currently only the actual user can add a dashboard or report to their favorites list. Developers can use the API to do this, but for normal admins provisioning users, they must log into each user account to set up the favorite/assigned dashboard and reports. Would be nice to have a way that composers or admins can assign on the user's behalf.

Currently if a user deletes a report from the Library it is gone forever and the only way to restore is via a database backup. This idea is to allow the ability to restore a deleted report either from a trash bin that admins have access to where deleted reports may remain for a specific time period until permanently removed. Please vote and leave your feedback on how you would like to see this feature implemented.