We have been running in a little bit of an issue. We have tried adding a binding to the report itself for culture to be linked to parameter but it wont change the culture of the report. We can set the binding on individual text boxes and it works fine. The other issue is from what we have found is that the culture of the report is supposed to be defaulted to the what the locale is for the computer that is running the report and we have a few international customers that are reporting that is not working.
Telerik Reporting Report Globalization - Telerik Reporting
When I launch the Telerik Report Designer i now get the the error below, also pictured in the attachment. I was able to launch and use the application once before, but now only get this error.
"An error has occurred while merging the resource dictionaries. Make sure that no assemblies with Telerik Controls for WPF reside in the same directory as the application executable.
Error of type 'Telerik.ReportDesigner.Core.AppResourceMergeException' was thrown."
This seems to be the same issue mentioned here in another question on this forum.
Below is the folder with the exe files for the application. I have tried restarting the computer, reinstalling the application, and repairing the application. None of these have fixed the issue.

I don't know exactly on which version when this functionality stop working but Telerik Report Viewer (HTML5) doesn't longer call /formats endpoint to get available formats on viewer initialization.
One workaround (or so) that we have found was to enable send email option to true (sendEmail: { enabled: true }) but this breaks our app as no email sending is required by our app users.
This is directly reproducible with build in CSharp.NetFramework.Html5IntegrationDemo and Telerik Report version 20.0.26.211 by changing
sendEmail: { enabled: true } on html js code.
Please advise.

Hello,
I want to generate a pdf file on the backend from a report that uses a SharedDataSource..
The report gets loaded with an instance of my implementation of the IReportSourceResolver.
The report uses a SharedDataSource. And I have also an implemenation of the ISharedDataSourceResolver configured.
I use the reporting engine in the following way:
ReportSource reportSource = _resolver.Resolve(reportName, OperationOrigin.GenerateReportDocument, resolvedParams);
var processor = new ReportProcessor();
var deviceInfo = new System.Collections.Hashtable();
RenderingResult result = processor.RenderReport("PDF", reportSource, deviceInfo);"telerikReporting": {
"processing": {
"sharedDataSourceResolver": {
"provider": "custom",
"parameters": [
{
"name": "typeName",
"value": "NameSpaceAndClassName, containing AssemblyName"
}
]
}
}
}
builder.Services.AddScoped<IReportServiceConfiguration>(sp =>
{
return new ReportServiceConfiguration
{
// ReportingEngineConfiguration = sp.GetService<IConfiguration>(), //(?? is this needed? does not load config either
Storage = new FileStorage(),
ReportSourceResolver = sp.GetRequiredService<DatabaseReportSourceResolver>()
};
});builder.Services.AddScoped<ISharedDataSourceStorage, DatabaseSharedDataSourceStorage>();
builder.Services.AddScoped<IReportDesignerServiceConfiguration>(sp => new ReportDesignerServiceConfiguration
{
DefinitionStorage = new DatabaseDefinitionStorage(sp.GetRequiredService<IReportDefinitionDataStore>()),
SharedDataSourceStorage = sp.GetRequiredService<ISharedDataSourceStorage>(),
SettingsStorage = new FileSettingsStorage(System.IO.Path.Combine(Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData), "Telerik Reporting")),
});Uncaught (in promise) RangeError: Maximum call stack size exceeded
at init.wrap (webReportDesigner.kendo-19.3.25.1111.min.js:16:433731)
at webReportDesigner.kendo-19.3.25.1111.min.js:16:432594
at Array.forEach (<anonymous>)export const ReportDesigner = (): React.ReactElement => {
const initializedRef = React.useRef(false)
useEffect(() => {
if (initializedRef.current) return
// Make jQuery global for legacy scripts
//@ts-expect-error: TS2339 (TS) Property '$' does not exist on type 'Window & typeof globalThis'.
window.$ = window.$ || $
//@ts-expect-error: TS2339 (TS) Property 'jQuery' does not exist on type 'Window & typeof globalThis'.
window.jQuery = window.jQuery || $
// Ensure Kendo exists globally
const kendo = window.kendo
if (!kendo) {
console.error("Kendo UI must be loaded globally before initializing the designer!")
return
}
const initDesigner = () => {
if ($("#reportDesigner").data("telerik_WebReportDesigner")) {
return // already initialized
}
//@ts-expect-error: TS2339 because Property 'telerik_WebReportDesigner' does not exist on type 'JQuery<HTMLElement>'.
($("#reportDesigner")).telerik_WebReportDesigner({
serviceUrl: "/api/ReportDesigner",
})
}
// Load Telerik designer scripts sequentially
const loadDesignerScripts = (): Promise<void> => {
return new Promise((resolve, reject) => {
if (document.querySelector('script[src*="webReportDesigner-19.3"]')) {
resolve()
return
}
const coreScript = document.createElement("script")
coreScript.src = "/telerik/webReportDesigner-19.3.25.1111.js"
coreScript.onload = () => {
const kendoScript = document.createElement("script")
kendoScript.src = "/telerik/webReportDesigner.kendo-19.3.25.1111.min.js"
kendoScript.onload = () => {
// Plugin should now exist
//@ts-expect-error: TS2339 (TS) Property 'telerik_WebReportDesigner' does not exist on type 'JQuery<HTMLElement>'.
if (!$.fn.telerik_WebReportDesigner) {
console.error("Telerik Web Report Designer plugin not loaded!")
reject(new Error("Telerik plugin not loaded"))
return
}
resolve()
}
kendoScript.onerror = (error) => reject(new Error(`Failed to load kendo integration script ${error}`))
document.body.appendChild(kendoScript)
}
coreScript.onerror = (error) => reject(new Error(`Failed to load core designer script ${error}`))
document.body.appendChild(coreScript)
})
}
// Ensure scripts loaded + token ready
loadDesignerScripts().then(() => initDesigner()).catch(err => console.error(err))
}, [])
return <div id="reportDesigner" style={{ height: "900px" }} />
}while active license is available:
public class CustomSharedDataSourceResolver : Telerik.Reporting.Processing.Data.ISharedDataSourceResolver
{
/// <summary>
/// Resolves and returns a DataSource instance from the provided <paramref name="sharedDataSourcePath"/> parameter.
/// </summary>
/// <param name="sharedDataSourcePath">The value of the Path property obtained from the report definition. Might be relative or absolute.</param>
/// <returns></returns>
public DataSource Resolve(string sharedDataSourcePath)
{
ValidateConfiguration();
var absolutePathToSharedDataSourceDefinition =
GetExistingFilePath(Configuration.Instance.ReportsPath, sharedDataSourcePath)
?? GetExistingFilePath(Configuration.Instance.SharedDataSourcesPath, sharedDataSourcePath);
[...]{
"ConnectionStrings": {[...]},
"AllowedHosts": "*",
"AzureStorageBlobConfig": {[...]},
"Logging": {[...]},
"TelerikReporting": {
"Processing": {
"SharedDataSourceResolver": {
"Provider": "custom",
"Parameters": [
{
"Name": "typename",
"Value": "TgsFlow.Plugin.Reporting.TelerikReporting.Utilities.CustomSharedDataSourceResolver, TgsFlow.Plugin.Reporting.TelerikReporting"
}
]
}
}
}
}Hello Telerik Support,
We’re implementing PDF accessibility in Telerik Reporting and enabled it via deviceInfo passed to RenderReport:
var deviceInfo = new Hashtable
{
{"EnableAccessibility", true},
{"Title", "CustomTitle"},
{"DocumentCreator", "CustomCreator."},
{"DocumentProducer", "CustomProducer."},
{"DocumentNaturalLanguage", "en-En"},
{"WriteDefaultAccessibleDescription", false},
{"FontEmbedding", "Full"},
};
var result = reportProcessor.RenderReport("PDF", reportSource, deviceInfo);After rendering document, document has accesability features but PAC (PDF checker for accesability) reports accessibility warnings related to tagged content structure.
In particular, text is split into multiple <Span> tags and link text is also tagged as <Span> instead of a link annotation <Link> element (example screenshot attached; sensitive data obfuscated).
We attempted multiple approaches to generate a proper link structure:
None of these produced a properly tagged link element in the output PDF.
Are we missing any additional configuration or a required reporting element setup to ensure hyperlinks are exported as proper link annotations/tags in accessible PDFs?
We’re using Telerik Reporting version 18.3.24.1218.
