Thank you for the feedback. Indeed, there is a learning curve when starting with our product, and it will be necessary to get used to some specifics. I hope the resources provided with the previous post will help. The REST Service is the application where our Reporting engine is running, and it is a must for the Html5 Web viewers.
Generally, the named connection string should be declared in the application configuration file, i.e. in an ASP.NET application, this would be the Web.config
file. In the case of the Standalone designer, this would be the Telerik.ReportDesigner.exe.config
file - by default in the (Telerik Reporting installation folder
)\Report Designer (e.g. C:\Program Files (x86)\Progress\Telerik Reporting R1 2019\Report Designer
The data saved in the User's local folder is the cache of the designer that holds the last opened reports, the configured data connections, etc. It may be deleted and will be regenerated upon re-opening the designer. The only consequence will be that the designer will have no history of what has been recently opened/created.
The approach we suggest for the multitenancy scenario is described in the Change Connection String dynamically through a report parameter
KB article. The only scenario it cannot be used is when the Report Parameters get their Available Values from a SqlDataSource, which connection string should also be provided dynamically.
You may consider opening a support ticket where to attach the project so that we may take a look at it and make more suggestions.
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal
and vote to affect the priority of the items