If I understood correctly, in the reportSource.report
it is necessary to pass a special Token that contains substrings that resemble URL encoded characters (e.g. '%2F').
I tested the scenario - I named a TRDP report "sp=r&st=2019-03-26T21:39:32Z&se=2019-03-27T05:39:32Z&spr=https&sv=2018-03-28&sig=6BSlZTyohlqKSSHFRCSj2Y%2BpmIiQ4LOB2M%2FmHnKrIdc%3D&sr=b.trdp" and passed it from the viewer to the REST Service. The built-in ReportFileResolver
was not able to find the report, as its name was encoded - here is the error message in the viewer:
Unable to get report parameters.
Report 'sp%3Dr%26st%3D2019-03-26T21%3A39%3A32Z%26se%3D2019-03-27T05%3A39%3A32Z%26spr%3Dhttps%26sv%3D2018-03-28%26sig%3D6BSlZTyohlqKSSHFRCSj2Y%252BpmIiQ4LOB2M%252FmHnKrIdc%253D%26sr%3Db.trdp' cannot be resolved.
In Fiddler the reportSource.report
appeared correctly :
Therefore, I created a custom report resolver
. The report
string was received as expected there, with no encodings or decodings. I was able to return a valid server-side ReportSource
based on this string.
I suggest to create custom resolver and handle report download there with custom code.
Please, test the suggested approach and let us know whether it works for you. If the problem persists, please, elaborate on the exact scenario. Consider also opening a support ticket and sending us the implementation of the REST Service and the viewer.
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