processing Element Overview
The Processing element specifies the configuration settings that will be applied during the processing of the report.
<processing> element
| Attributes |
|
| Child elements |
|
| Parent element | Telerik.Reporting - specifies the root element of the Telerik Reporting configuration settings. Only one <processing> element can be used in the Telerik.Reporting element. |
Example
<Telerik.Reporting>
<processing cacheDefinitionProperties="false" allowCultureDependentDataFieldNames="false" traceVerbosity="Info" validateReportPaths="true">
<!--The element below sets the graphics engine used for measurement and rendering.
Available values for engineName: "Skia", "Gdi", "PlatformDependent". Default value: PlatformDependent.-->
<graphicsEngine engineName="PlatformDependent">
</graphicsEngine>
<!--The element below represents a collection of explicitly allowed UNC (network) paths for
report document resolution when the attribute validateReportPaths is enabled (default):-->
<externalReportPaths>
<add value="\\fileserver\reports"/>
<add value="\\backupserver\shared\reporting"/>
</externalReportPaths>
<!--The element below represents a Path resource resolver:-->
<!--<resourceResolver provider="path">
<parameters>
<parameter name="directory" value="c:\\CommonResourcesDirectory\\" />
</parameters>
</resourceResolver>-->
<!-- The element below represents a custom implementation of resource resolver-->
<!--
The typeName should include first the class of the custom ResourceResolver(including the namespace) and
the second part, separated by a comma, is the name of the assembly that will contain that code(can be the same
project) e.g. "CSharp.Net8.Html5IntegrationDemo.CustomResourceResolver, CSharp.Net8.Html5IntegrationDemo"
-->
<resourceResolver provider="custom">
<parameters>
<parameter name="typeName"
value="Namespace.CustomResourceResolverClass, AssemblyName"/>
<parameter name="constructorParameter1"
value="constructorParameterValue1"/>
</parameters>
</resourceResolver>
<!-- The element below represents a custom implementation of a sharedDataSource resolver-->
<!--
The typeName should include first the class of the custom ResourceResolver(including the namespace) and
the second part, separated by a comma, is the name of the assembly that will contain that code(can be the same
project) e.g. "CSharp.Net8.Html5IntegrationDemo.CustomSharedDataSourceResolver, CSharp.Net8.Html5IntegrationDemo"
-->
<sharedResourceResolver provider="custom">
<parameters>
<parameter name="typeName"
value="Namespace.CustomSharedDataSourceResolverClass, AssemblyName"/>
<parameter name="constructorParameter1"
value="constructorParameterValue1"/>
</parameters>
</sharedResourceResolver>
</processing>
</Telerik.Reporting>CacheDefinitionProperties
We provide a mechanism for caching the report definition properties that boost performance. Naturally, it prevents modifying the report during the processing stage. The default value of the property is True.
The Report Events are not intended to be used to modify the report definition, as explained in the Understanding Events article. For that reason, in R3 2016 (10.2.16.914), we introduced a change - cacheDefinitionProperties which caches the report definition properties, so such modifications are not respected. Setting the cacheDefinitionProperties to false will skip the definition item properties caching, which will allow the report definition to be changed in the report events. This may result in a performance penalty, though.
Starting with R3 2022 SP1 (16.2.22.1109), CacheDefinitionProperties was exposed as a Report definition property in the ReportEngineSettings properties collection, so that you may specify it per Report. The property value may be set to Default, True, or False. The Default, which is the default value, lets you specify that the Reporting engine should respect the cacheDefinitionProperties set in its configuration on the project level.
Graphics Engine
The graphicsEngine element was introduced with the Skia graphics engine in R3 2023 (17.2.23.1010). It sets the graphics engine used for processing and rendering the reports. There are two implementations of the graphics engine: GDI-based and SkiaSharp-based. GDI is not supported on non-Windows platforms for applications that target .NET 8 or higher. Skia implementation has cross-platform support. The active implementation is determined by the value of the engineName element, which corresponds with the members of the Telerik.Drawing.Contract.GraphicsEngine enumeration.
If the graphicsEngine element is not present in the configuration file, the PlatformDependent value will be used. Skia implementation is not available in applications that target the .NET Framework. They can only work with the GDI graphics engine.
<graphicsEngine> element
| Attributes | engineName – required string attribute. Determines the type of Telerik.Drawing.Contract.GraphicsEngine used in the application. Available values:
|
Validate Report Paths
By default, the declarative report definitions (TRDP, TRDX, and TRBP files) can be resolved only from paths within the application hosting the Reporting Engine when using ReportProcessor or embedded Reporting Engine with the desktop viewers; the UriReportSourceResolver when using Reporting REST Services; and those specified in the externalReportPaths element. The attribute validateReportPaths lets you allow all external paths by setting it to false (the default is true).
<externalReportPaths> element
Add external UNC (network) paths for report document resolution. The collection is taken into account only when the optional attribute validateReportPaths is enabled (default).
ResourceResolver
resourceResolver element allows to alter the default resource-resolving mechanism. This element determines which implementation of the Telerik.Reporting.Interfaces.IResourceResolver interface will be used by the processing engine to resolve the resources that are specified in the report definition. Such resources are:
- Images used by Telerik.Reporting.PictureBox and Telerik.Reporting.CheckBox report items, referenced by a relative path.
- Elements from the report's Telerik.Reporting.Drawing.ExternalStyleSheet collection, referenced by a relative path.
- Source property of Telerik.Reporting.CsvDataSource and Telerik.Reporting.JsonDataSource report items, referenced by a relative path.
This ResourceResolver is intended to be used in scenarios where the resources are not retrieved from a local file path but rather obtained from a different type of storage. As an example, Telerik Report Server persists its assets in storage that can be file-based or use an MSSQL or Redis database as a backend. Processing a report definition that has relative paths to its resources would not work in this scenario unless the necessary resources aren't placed in folders relative to the root of the Telerik Report Server web application. The custom resource resolver can be used here to provide specific logic that will retrieve the necessary resources as byte arrays using the resource identifier from the report definition.
Restricting External Resource Access
Telerik Reporting introduced IStrictResourceResolver in the 2026 Q4 (20.3.26.1110) release.
Implement Telerik.Reporting.Interfaces.IStrictResourceResolver to apply your own rules to all external report-resource references handled by the resource readers. This interface extends IResourceResolver and adds no members; implement Resolve(string resourceUri).
The existing interface handles selected references, including relative image paths. Absolute locations and resources such as map tiles do not all pass through it. The strict interface extends coverage across relative paths, absolute paths, UNC paths, and URLs.
Strict resolution covers the following external resources:
- Images, including external image references in HTML and SVG content.
- CSV and JSON data source files.
- Shapefiles and their companion DBF files.
- External stylesheets.
- Map tiles, metadata, and logos.
The following table describes the authoritative result of Resolve:
| Result | Behavior |
|---|---|
byte[] | Uses the returned bytes as resource content. |
string | Reads the resource from the approved path or URL. |
null | Denies access without a fallback to the original resource location. |
Telerik Reporting does not provide a ready-to-use public strict resolver implementation. Validate paths and URLs in your custom code before returning content or a location.
Keep validateReportPaths enabled for report definitions. The strict interface does not supply a validation policy or automatically apply validateReportPaths and externalReportPaths to custom results.
Inline content and assembly-embedded resources do not necessarily require an external lookup. Report-source selection and data-provider connections remain separate responsibilities.
Register the strict implementation with the existing custom provider and its assembly-qualified typeName. No new provider or configuration switch is required. Existing IResourceResolver implementations remain supported.
Register the custom type in typeReferences so the engine can activate it with type validation enabled.
For a complete C# implementation and XML/JSON registration examples, refer to Restricting Access to Report Resources. The sample permits files beneath one configured local directory and PNG images directly in a trusted HTTPS folder. Its REST service uses the built-in UriReportSourceResolver for a local TRDP with data-bound images; report-source resolution remains separate.
<resourceResolver> element
| Attributes | provider – required string attribute. Determines the provider type of the ResourceResolver instance. Only two types are supported:
|
| Child elements | parameters – specifies a collection of parameters for the resource resolver in the <resourceResolver> element. Only one parameters element can be used in the <resourceResolver> element.Supported parameters for path provider
|
| Parent element | processing - specifies the parent element of the Telerik Reporting configuration settings. |
<<<<<<< Updated upstream
SharedDataSourceResolver
=======
Resource Resolver Providers
The provider attribute supports the following types:
- path - Specifies to use an internal ResourceResolver instance that will resolve the resources from a given directory specified in the
<parameters>element. - custom - Specifies a custom implementation of Telerik.Reporting.Interfaces.IResourceResolver, including implementations of
IStrictResourceResolver. The engine instantiates it at runtime from the type name in the<parameters>element.
Supported Parameters for the path Resource Resolver Provider
Set the following parameter in the <parameters> collection:
- name: directory
- value: the path to the directory that contains the resources to be resolved.
Supported Parameters for the custom Resource Resolver Provider
Set the following parameter in the <parameters> collection:
- name: typeName
- value: the assembly qualified name of the type that implements the Telerik.Reporting.Interfaces.IResourceResolver interface.
The parameters collection of the custom provider can contain additional entries that will be passed to the constructor of the type. The provider excludes typeName, sorts the remaining entries by parameter name, and passes their values as positional string arguments. If no additional parameters are specified, the parameterless constructor will be used.
SharedDataSourceResolver
Stashed changes
sharedDataSourceResolver element allows to alter the default shared DataSource(.sdsx)-resolving mechanism. This element determines which implementation of the Telerik.Reporting.Processing.Data.ISharedDataSourceResolver interface will be used by the processing engine to resolve the shared DataSources references that are specified in the report definition.
This SharedDataSourceResolver is intended to be used in scenarios where the .sdsx files are not retrieved from a local file path but rather obtained from a different type of storage. As an example, if a custom Telerik.WebReportDesigner.Services.ISharedDataSourceStorage is implemented where the .sdsx files are stored in a database, then a custom SharedDataSourceResolver would be necessary to provide specific logic that will retrieve the .sdsx XML from the database and will then Deserialize it to an instance of the Telerik.Reporting.DataSource class and return it in the Resolve method.
<sharedDataSourceResolver> element
| Attributes | provider – required string attribute. Determines the provider type of the SharedDataSourceResolver instance. Only two types are supported:
|
| Child elements | parameters – specifies a collection of parameters for the resource resolver in the <sharedDataSourceResolver> element. Only one parameters element can be used in the <sharedDataSourceResolver> element.Supported parameters for path provider
|
| Parent element | processing - specifies the parent element of the Telerik Reporting configuration settings. |