Hi,
I am using your HTML5 report viewer, along with WebAPI REST service (Q2 2014).
I am getting an issue where, when linking through to a second report, it is adding "C:\" as a prefix to the report name.
E.g.
A report "Header.trdx", which links through to "Lines.trdx". The report viewer is asking for report "C:\Lines.trdx".
Having looked at the xml behind the report, the link/action is defined as "<UriReportSource Uri="Lines.trdx">"..
Do you know why this might be happening?
Might it be something to do with how I've setup my implementation?
Is anyone else having a similar issue?
Thanks
Tom France
I am using your HTML5 report viewer, along with WebAPI REST service (Q2 2014).
I am getting an issue where, when linking through to a second report, it is adding "C:\" as a prefix to the report name.
E.g.
A report "Header.trdx", which links through to "Lines.trdx". The report viewer is asking for report "C:\Lines.trdx".
Having looked at the xml behind the report, the link/action is defined as "<UriReportSource Uri="Lines.trdx">"..
Do you know why this might be happening?
Might it be something to do with how I've setup my implementation?
Is anyone else having a similar issue?
Thanks
Tom France
3 Answers, 1 is accepted
0
Hi Tom,
when you deploy the TRDX files, they must be in the same relative position at the time you designed them. You can also use expressions to route reports e.g., a report parameter which points the server location of the file: =Parameters.Parameter1.Value+'MyReport.trdx'. Then report parameters' values can be left to default values or passed externally.
I hope the above information is helpful.
Regards,
Stef
Telerik
when you deploy the TRDX files, they must be in the same relative position at the time you designed them. You can also use expressions to route reports e.g., a report parameter which points the server location of the file: =Parameters.Parameter1.Value+'MyReport.trdx'. Then report parameters' values can be left to default values or passed externally.
I hope the above information is helpful.
Regards,
Stef
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0
Tom
Top achievements
Rank 1
Rank 1
answered on 30 Oct 2014, 08:47 AM
Hi Stef,
Thanks for your response.
I'm not sure you've answered the correct post here.
Also, my other post seems to have gone missing. They were two separate issues. The other was about the relative paths in trdx files, which this seems to be a response for.
Can you check what happened to the other post? I know I put it on twice, as i kept getting an error page when trying to post, so kept trying.
Thanks
Tom
Thanks for your response.
I'm not sure you've answered the correct post here.
Also, my other post seems to have gone missing. They were two separate issues. The other was about the relative paths in trdx files, which this seems to be a response for.
Can you check what happened to the other post? I know I put it on twice, as i kept getting an error page when trying to post, so kept trying.
Thanks
Tom
0
Hello Tom,
Your other question is regarding relative paths and how they are resolved on processing a TRDX file. All relative paths are resolved based on the start application, where if the service is hosted in separate project, the start location is the service project's execution folder.
To manually route relative paths, you can use the suggested approach - to append a string parameter to the relative path in an expression, where the parameters value points the base path to the resource.
In addition, I have converted your other post into our system. If you need further help, please use it to provide more details about the issue.
Regards,
Stef
Telerik
Your other question is regarding relative paths and how they are resolved on processing a TRDX file. All relative paths are resolved based on the start application, where if the service is hosted in separate project, the start location is the service project's execution folder.
To manually route relative paths, you can use the suggested approach - to append a string parameter to the relative path in an expression, where the parameters value points the base path to the resource.
In addition, I have converted your other post into our system. If you need further help, please use it to provide more details about the issue.
Regards,
Stef
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.