Difference between revisions of "Dashboard widget configuration"

From TempusServa wiki
Jump to navigation Jump to search
old>Admin
old>Admin
Line 7: Line 7:
* Aggregated values (charts, tables or number)
* Aggregated values (charts, tables or number)


For List of records  
For '''List of records'''
* Fields displayed in list ?
* Fields displayed in list ?
* Sorting field ?
* Sorting field ?


For Aggregated values
For '''Aggregated values'''
* Categorization ? (group by another fields value)
* Categorization ? (group by another fields value)
* Metric ?  
* Metric ?  
Line 20: Line 20:
** Icon on button ?
** Icon on button ?


First consider which filters limit the data
Next consider which '''filters''' limit the data
* Period ranges ?
* Period ranges ?
* Status limitations ?
* Status limitations ?

Revision as of 17:28, 6 January 2021

Asking the right questions

To add the right content into dashboards widgets you will need to define what should be displayed

First choose the output

  • List of records
  • Aggregated values (charts, tables or number)

For List of records

  • Fields displayed in list ?
  • Sorting field ?

For Aggregated values

  • Categorization ? (group by another fields value)
  • Metric ?
    • Field
    • Method (sum, average, min, max)
  • Link to detailed data ?
    • URL to link to ?
    • Icon on button ?

Next consider which filters limit the data

  • Period ranges ?
  • Status limitations ?
  • User relation information ?

In case you are generating normal record lists no effort is required for security filters and hiding deleted items.

Configuration help

Buttons

All the below properties are required for the button

  • ButtonGlyph: Icon of the button (3 options)
  • Title: Text below the icon
  • Content: Url of the button

Optimally buttons are places in the Toolbar zone on the page, where they are rendered as normal buttons. If placed in other zones they are rendered as large squares.

SQL Query

An SQL Query may extract almost anyting from the database.

This process ignoreres the security restrictions in the system, so you will have to implement them yourself (see special keyworkds below).

Sample: Limited status distribution

The following example displays quite well in a pie chart.

 SELECT s.Status, count(*)
 FROM data_leads1 as d
 JOIN formstatus as s ON  s.StatusID = d.StatusID 
 WHERE d.StatusID IN (11344,11343,11345)
 GROUP BY 1

Special keywords / variables

  • %UserID%
  • %ExclusiveGroupID%
  • %GroupListSql%
  • %ExclusiveGroupListSql%
  • %AndRecordFilter%

Lists

To setup a list view, simple copy/paste the URL of a view.

Optimally you should strip anything but the parameters from the URL

  ?SagID=252&command=list&QUERY_FIELD_1=OPFLGNING& ...


Special case: List of values i search parameters

Currently lists of search parameters are encoded

 ... &QUERY_VALUE_3=11344%2C11343%2C11345& ...

To make them work in list views, please decode the kommas

 ... &QUERY_VALUE_3=11344,11343,11345& ...

(just change "%2C" to ",")


Other widgets

Codeunit

This widget displays raw HTML ouput from any PageContentCodeunit.