...
The stored procedure must have these input parameters no matter how they are used in the reporting logic.
| Parameter | Nullable | Description |
|---|---|---|
| @startDate datetime | No | The start date of the reporting period. |
| @enddate datetime | No | The end date of the reporting period. |
| @categories nvarchar(max) | Yes | Selected category list separated by a comma, e.g. 'Salesforce Opportunities', 'Purchase Orders' |
| @users nvarchar(max) | Yes | Selected user names separated by a comma, e.g. 'Approver1', 'Approver2' |
| @platforms nvarchar(max) | Yes | Selected task action platform list separated by comma, e.g. 'Web', 'Mobile' |
...
The following two extended properties are required for the stored procedure to be selected for reporting:
- Description;
- Purpose : - must be one of the following:
- UsageReport - the stored procedure must implement the chartable report specification below;
- Export - export only, the stored procedure can produce any result table.
...
For on-screen chart, the stored procedure must produce the following two tables in the order as a result:
- The first table contains the charting meta datametadata:
| Column | Value | Description |
|---|---|---|
| seriesLabel | The name of a column in the data table. | Value of this column is grouping for the data series. |
| xfield | The name of a column in the data table. | Value of this column is used to plot the x-axis |
| yfield | The name of a numeric column in the data table. | Value of this column is used to plot the y-axis |
| charttype | Fixed string value. | The default chart type. Must be one of the following:
|
| stack | Fixed number. | 0/1 whether the chart should stack the data series. |
- The second table is the data table. This table must have
- at lease least one numeric column that can be used for the y-axis in the chart;
- at lease least two other columns to be used for gouping grouping the data series and the x-axis in the chart.
...