- Steve McNiven
So jump in the way back machine, Sitefinity v4 shipped with a (really bad\buggy) eComm module. However part of that module was reporting using the Telerik.Reporting assemblies. Sometime around v12 or 13 they decomissioned the old eComm module (in favour of uCommerce), and subsequently stopped shipping the Telerik.Reporting DLLs with Sitefinity.
Well, I had to do some more reporting UIs, so we re-licensed the product so we could get the latest v15 assemblies and (more importantly) get access to the Visual Studio 2022 reporting designer. It’s not REQUIRED to generate a report, you can do it all through code, but it does simplify it quite substantially.
So the most important part is to follow the installation doc the provide, but when you come to the part about registering routes IGNORE IT! It’ll tell you to just call this
However when Sitefinity tries to load it’ll crash right away because some of the default route names conflict with Sitefinity. What we have to do instead is manually register them, and here it is! Just call this in Global.asax INSTEAD if the ReportsControllerConfiguration.RegisterRoutes that they provide.
So for the viewer part, here’s the setup doc but I’ll also post my Vue implementation here (still uses some jQuery, viewer requires it…). Feel free to use or not, and\or tweak. It is a shareable vue component I use inside other REPORTNAME.cshtml files like this
<telerik-report-viewer ref="viewer" v-if="renderReport" :params="params"></telerik-report-viewer>