Difference between revisions of "Features/Dashboards"
(Created page with "== Usage == == AI assisted reporting == == Personalized content == Note that users in addition to dashboards also can save their own searches and list views: Features/Personal_views") |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Usage == | == Usage == | ||
Dashboards are informationaly boards consisting of a multitude of widgets. | |||
We often seggrate dashboards into | |||
* Operational dashboards | |||
* Management dashboards | |||
== | == Widgets for everything == | ||
TS has a long list of content | |||
* List of items to handle | |||
* Aggregated data | |||
** Graphs | |||
** Tables | |||
* Shortcut buttons | |||
** Adding registrations | |||
** Performing searches | |||
* Custom parts | |||
** SQL views | |||
** Codeunits | |||
* Context selectors | |||
== | Access to all widgets are controlled via groups, and the Dashboard will automatically layout the content to each user. | ||
Note that users | |||
== AI assisted reporting == | |||
Advanced reporting will often require complex queries to get and illustrate the data that you want. | |||
TS has an AI assisted query builder that can be promted using clear text | |||
Give me Top 10 customers where order sums are larger than 10000, for orders in the current month | |||
This will generate the required query, display in a digram and all you need to do is to click: Add as widget | |||
'''Please note: Your data is never in contact with the underlying language model''' | |||
== Customized content == | |||
All views can support the following references | |||
* "ME": Placeholder parameter for the current user | |||
* NUMBER: Relative reference for time (0 = today, 1 = tomorrow etc.) | |||
In order to handle permisisons gracefully across different users types, data ownership filter tags can be inserted into SQL statements. | |||
Note that users can also save their own searches and list views: [[Features/Personal_views]] | |||
Latest revision as of 10:05, 10 November 2024
Usage
Dashboards are informationaly boards consisting of a multitude of widgets.
We often seggrate dashboards into
- Operational dashboards
- Management dashboards
Widgets for everything
TS has a long list of content
- List of items to handle
- Aggregated data
- Graphs
- Tables
- Shortcut buttons
- Adding registrations
- Performing searches
- Custom parts
- SQL views
- Codeunits
- Context selectors
Access to all widgets are controlled via groups, and the Dashboard will automatically layout the content to each user.
AI assisted reporting
Advanced reporting will often require complex queries to get and illustrate the data that you want.
TS has an AI assisted query builder that can be promted using clear text
Give me Top 10 customers where order sums are larger than 10000, for orders in the current month
This will generate the required query, display in a digram and all you need to do is to click: Add as widget
Please note: Your data is never in contact with the underlying language model
Customized content
All views can support the following references
- "ME": Placeholder parameter for the current user
- NUMBER: Relative reference for time (0 = today, 1 = tomorrow etc.)
In order to handle permisisons gracefully across different users types, data ownership filter tags can be inserted into SQL statements.
Note that users can also save their own searches and list views: Features/Personal_views