This is the text that will be displayed as a field label or a table column header in a tabular report. To replace the default caption with one customized for your reports, simply overwrite the default text.

The caption field becomes the x-axis label. For Line Charts, the label can be any object, such as a master server. When charting performance metrics for an object, a date field should be configured as a label. See Line Charts for Performance Metrics.

When the report template has the “Display as” component set to Table, the following Type options are available.

When the report template has the “Display as” component set to Bar Chart, the following Type options are available. See also Configure a Bar Chart Dynamic Template, Steps to Create a Bar Chart Dynamic Template, and Examples of Bar Chart Dynamic Templates.

When the report template has the “Display as” component set to Line Chart, the following Type options are available. See also Steps to Create a Line Chart Dynamic Template, Line Charts for Performance Metrics, and Examples of Line Chart Dynamic Templates.

When the report template has the “Display as” component set to Area/Stacked Area Chart, the following Type options are available. See also Configure an Area/Stacked Area Chart Dynamic Template.

When the report template has the “Display as” component set to Pie Chart or Donut Chart, the following Type options are available. See also, Examples of Pie Chart Dynamic Templates and Example of a Donut Chart Dynamic Template.

The formatter list includes only values relevant for the field. For example, numeric fields have only numeric formatters listed, such as Number, Currency, and File Size. Valid formatters include: Date, Date + TimeZone, Date Group By, Numeric, Decimal, Speed, Currency, File Size, Time Duration, Char Substitute, Unit Converter, File Size No Label, Null Substitute, Time Elapsed, Cron Schedule, Yes/No, Percentage, Status Icon, Full Name, Area Sparkline, and Column Sparkline.

See also, Valid Formatter Patterns and Create a Sparkline Chart in a Tabular Dynamic Template.

Enter a specific pattern for the formatter to customize the default format. Example: KiB::GB or KB::_

See Valid Formatter Patterns.

The default value provides the most common usage. For example, numeric values typically should be right-aligned so that decimal points line up.

Select Yes if you want long values/text to wrap in the space provided in the report. When No is selected, the data will extend horizontally.

Total/Subtotal Options: Null, Sum, Average, Minimum, Maximum.

Use this configuration to aggregate the values, such as all the backup job sizes for a backup server. In its simplest form, this aggregation is used to display grand totals for all the data displayed in a tabular report.

* Never configure Total/Subtotal and Column Break = Yes for the same field.

Select Yes if you want to list subtotals at the end of a group of related fields. Note that when you use subtotals, the sort order is automatically determined. All fields with a Column Break selection are sorted in the relevant ascending order and this sort order cannot be changed. Be sure not to remove or modify this sort order.

Example: You could create a tabular report for client, server, and kilobytes. Then, you could subtotal on server to aggregate the kilobytes per server.

* Never configure Total/Subtotal and Column Break = Yes for the same field.

* Once you configure a subtotal, you can no longer create grand total rows at the end of the tabular report template.

--------------------------------------------------------------------------------------------------------

For line charts, the column break is required if the selected object is potentially not unique. To ensure uniqueness, you may need to include a unique ID field with the Column Break set to Yes. For example, an array name may not be unique, however, the array ID is sure to be unique. Include both the name and ID in the template, but make the ID a hidden field with the Column Break set to Yes. See also, Field Configuration for One Object Per Line Chart.

Select the report to which this field will link. This takes you to the Drilldown Configuration window. See Dynamic Template Drilldown Configuration.

For a list of out-of-the-box report templates that have drilldowns that you can use as examples, see Examples of Dynamic Templates Containing Drilldowns.

A drilldown condition lets you control cases where a drilldown doesn’t make sense to be displayed, for example, null or 0 values for a field. For example, you wouldn’t want to drill down on a Job ID for a row if the value of Job ID returned from the database is Null or 0 (zero).

Example: ${row['B'] != '0'}

where B is the alias name

In this example, the drilldown link will appear only when the returned value is not zero.

Example: Configure a drilldown on field D and enter a drilldown condition as shown in the following example. In this example, if the row where the value of the field aliased as A is NULL, the value in column D will not have a drilldown URL enabled.

Example: Multiple conditions can be configured.

Use this option to configure the background color of a cell in a tabular report.

Example:

where C is the alias of the selected field.

This is applicable only for Date fields in Bar, Line, and Pie Chart report templates to aggregate data for charting. If only one date field is specified, it is used as the default for the Group By Date configuration.

If you configure a date field as a caption, Group by Date is automatically set to Yes. If there are multiple date fields in a template, you must choose only one for this setting.

This Group by Date setting identifies the field that the scope selector will use with the Group By scope component. When this Group by Date element is set to Yes, the Group By component in the Scope Selector is automatically selected.

Use the Time Period Date selection in report templates to designate which date field will be used for the Time Period scope. If only one date field is included in the template, that field is used as the default. If more than one date field is defined in a template, only one date field can have this Time Period Date set to Yes.

The Time Period Date must be set to Yes for one of the date fields in the template when a Time Period, but no Group By is selected in the scope selector. This configuration enables grouping of raw, non-aggregated data.

Time Period Date can be set for displayed, hidden, or excluded date fields.

Currently, this option is available only for storage arrays and objects created via the SDK.

Enter a description to be displayed when a user hovers the mouse over an image in a report; for example, use this setting to enable mouse-overs on lines in bar charts, lines in line charts, and even images in table columns.

Example: Available: ${row['Q1']}

where Q1 is the alias name.

See also, Examples of Dynamic Templates Containing Graphics Tool Tips.

For text fields only. Use this option if data returned for a field has multiple values that need to be separated by commas. Only the names will be shown in the rendered report and the IDs will be used for drilldowns, if drilldowns are configured.

This is the description supplied by the Data Dictionary for this field. You can overwrite or supplement this text. This description will be displayed when a user hovers the mouse over the field or table column label in a report. It will also be incorporated into the context-sensitive help that is displayed from the Help button. See Quick Start Step 6: Generate a Report and View the Automatically Generated Help.