Note: I'm brand-new to Telerik Reporting development.
I am trying to build a user function that our report builders can use when building reports to do some special formatting, timezone handling, etc. This assembly that I am building will need to be deployed/installed on the report server that is running Telerik Reporting Server so that our report builders can leverage the new functionality provided by my assembly containing the custom user functions.
I am trying to figure out how to give my new class library project access to the Telerik.Reporting.Expressions namespace. Specifically, I need Telerik.Reporting.Expressions.FunctionAttribute and some other custom attributes.
Assembly: Telerik.Reporting (in Telerik.Reporting.dll)
I have an urgent need to deploy Report Server on 2 different server nodes, with load balancing.Does Reports Server support that, and how do I go about replicating reports/data sources across the 2 nodes.
We have reports deployed to a report server and they've been working great. All of the sudden, they are now throwing an error: Error loading the report viewer's templates. (Template = http://server/api/reports/resources/templates/telerikReportViewerTemplate-html). In dev tools it has: XMLHttpRequest cannot load http://server/api/reports/resources/templates/telerikReportViewerTemplate-html. The 'Access-Control-Allow-Origin' header has a value 'http://localhost:10969' that is not equal to the supplied origin. Origin 'http://someOtherServer' is therefore not allowed access.
We call the reports from two different domains (azurewebsites and then a custom subdomain). How can we accomplish this?
I will start the trial and have several questions about our requirements
What is a prefer way the deploy the report server to Azure?
I not found any example how to use report server as docker container
We use Team Services for deploying our services. Is there any way to change the connection strings during deploying, today the prefer way is environment variables.
Is there multi tenancy support?
We use Telerik Report Server in connection with our web gis system, and users are managed in this system.
When we fetch a report, it's done with a GET, which enables the user to "hack" the parameter values that are attached. This is not desireable.
1st question: How come TRS only allows reports to be executed using GET ?
Adding POST would enable us to hide the parameters.
2nd question: Why does TRS add all parameters to the URL in the address bar, when executing the report, even those that aren't given originally and not visible ?
This make hiding parameter values from users very difficult.
It seems that the report server web interface has a bug.
When I upload two versions of these same report (but with internal differences), with identical names but in different categories, it works just fine.
But if I try to edit the description of either in the web interface, it throw an error about multiple report with identical names.
How come the web interface doesn't include the category in this assesment ?
I've created a report with a number of multi-value parameters. This works just fine in the Report Designer preview. Image3
I then published it to our report server, andright off it seems to work (all parameters select all distinct values) Image1
But if I select a subset of certain values for one of the parameters, the report server viewer fails with system error message: "Missing or invalid parameter value" Image2
It varies which combination exhibit this behaviour.
After having purchased and used Telerik Reportserver for almost a year now, we've come across multiple problematic designs in TRS.
The worst issue was our attempt to delete the built-in "Guest" account (via REST, tidying up unnecessary users), which resulted in its user name being wiped, and it being reactivated (was deactivated).
This result crashed the server software repeatedly, and we had to reinstall a backup of the server database to fix it. Why is it even possible to make changes to a built-in account, that clearly is essential to the workings of TRS ?
Other grievances include:
- The inability to delete users in the web interface.
- The very limited dropdown width for reports, showing only a small part of the names, when we use long category and report names.
- Missing sensible sorting of various lists, rendering them very troublesome to navigate.
- The inability to exclude certain reports from sharing (via the Guest account), forcing us to instead add a lot of reports on the account's permissions (90%/10% problem).
- The locking of server reports after publishing a report from the stand-alone Designer, always requiring the Designer to be shut down and restarted to release the lock.