New to Telerik Reporting? Download free 30-day trial
Telerik script language provides the following intrinsic (or "built-in") objects that may be used in Expressions inside the report definition.
The Fields collection represents the set of fields specified by the report data source plus any additional calculated fields that you create. After you create a data source for a data item (Report, Table, Crosstab, List, Chart), the field collection appears in the Data Explorer toolbox.
- returns the value of the field ProductID in the current data
scope instance. If the data source does not contain the
referenced column, error is thrown. If the report has no data
source set, the expression result is null (Nothing)
If the data source field name is not a valid name in terms of programming languages (contains spaces, punctuation marks, etc.) enclose its name in square brackets, for example =Fields.[My Column]; Because brackets are special characters, you must use a back slash ('\') to escape the bracket, if it is part of a data field name. For example, a data field named Field would be referenced as Fields.[Field\[1\]].
Another option of accessing the values in the fields collection is the global function Fields(fieldName).
represents the collection of report parameters, each of which can be single-value or multi-value. See Adding Parameters to Report.
- returns the value of the report parameter with name Product;
=Parameters.Product.Label - returns
the label of the report parameter with name Product.
Another option for accessing the report parameters' collection is the global function Parameters(parameterName).
The current page number that can be used only in page header and footer.
The total number of pages in the report that can be used only in page header and footer.
The page numbering behavior in a report contained in a report book may be controlled through the PageNumberingStyle property.
Represents the runtime rendering extension currently used to render the report.
For information regarding the available child properties, check out the RenderingFormat API reference or use the Expression Builder dialog.
This global object will be populated while rendering the report in any report viewer or programmatically. The object will not be available in the ReportParameters properties evaluation as the parameters get evaluated before the rendering operation gets started.
It is strongly recommended to use this property only for report visual output customizations and not for data retrieval parameterization, as the report data gets cached between the rendering operations for desktop viewers. Thus, using it will not lead to the desired effect.
The current processing item in which context the expression is evaluated. The object is not evaluated when the processing item is not available, i.e. when using it in report parameters.
For information regarding the available processing ReportItem properties, check out the corresponding processing item API reference.
The current report definition.
For information regarding the available Report definition properties, check out the Report API reference.
Represents the current user identity in which context the expression is evaluated.
For information regarding the available child properties, check out the UserIdentity API reference or use the Expression Builder dialog.
This global object will be populated for all web report previews based on the HTML5 report viewer. The default user identity resolution can be substituted for each reports rendering service by overriding the corresponding GetUserIdentity method.
When exporting a report programmatically the global object can be populated by setting the static property UserIdentityCurrent.