Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Look into allowing Drilldown reports to work properly #27

Open
alanjuden opened this issue Apr 5, 2017 · 9 comments
Open

Look into allowing Drilldown reports to work properly #27

alanjuden opened this issue Apr 5, 2017 · 9 comments
Labels

Comments

@alanjuden
Copy link
Owner

@alanjuden alanjuden commented Apr 5, 2017

No description provided.

@Kaugustine01

This comment has been minimized.

Copy link

@Kaugustine01 Kaugustine01 commented Apr 11, 2017

Im excited for this enhancement. What are your thoughts on feasibilty and timing?

@alanjuden

This comment has been minimized.

Copy link
Owner Author

@alanjuden alanjuden commented Apr 12, 2017

@Kaugustine01, I'm not sure on the feasibility and timing. I've been pretty busy lately so I haven't yet had a chance to look into it, but hopefully some evening soon I'll get to mess with the idea.

@fluentsolutions

This comment has been minimized.

Copy link

@fluentsolutions fluentsolutions commented Jun 10, 2017

@alanjuden I am looking into implementing this as well as the show/hide toggles but I can't seem to find documentation around how to make the generated HTML include identifiers or if this functionality even exists. What documentation were you using to help you? I have looked through all of the technet docs and can't seem to pinpoint how to define show/hide toggles. If I figure it out I can contribute the code back.

@fluentsolutions

This comment has been minimized.

Copy link

@fluentsolutions fluentsolutions commented Jun 11, 2017

From what I can tell you can't utilize the interactive features with HTMLFragment=true. Have you come across anything that would suggest this is possible?

@alanjuden

This comment has been minimized.

Copy link
Owner Author

@alanjuden alanjuden commented Jun 12, 2017

@fluentsolutions, I had done some research on this a month or so ago and wasn't ready to call it quits on figuring out a solution for it...but from what I'm seeing it doesn't really seem very feasible.

@fluentsolutions

This comment has been minimized.

Copy link

@fluentsolutions fluentsolutions commented Jun 12, 2017

I had to revert to using the ReportViewerControl in a Webform within MVC. I researched and it looks like it is not possible to leverage interactive functions when HTMLFragment = true.

@ivancogeorgiev

This comment has been minimized.

Copy link

@ivancogeorgiev ivancogeorgiev commented Apr 5, 2019

We solved the problem with the drill-down by parsing the HTML content and attaching javascript function on each of the drill-down links.
This javascript function sends GET request to the Reporting Server (via our API since we need to set credentials) and fetches the report content in HTML format.
We are aware that with this solution we are losing the paging feature but for our case, this is not very important since the reports are not that large. Drill-down reports are always shown on one page.

For the drill-down reports, we overrode the print and export features of the viewer.

We resolved toggling and sorting for the drill-down reports in a similar way: from the drill-down HTML report content we extract the execution id. This id is required for the Reporting Server to process the sorting/toggling request and return new HTML report content.

The second and last limitation we have (besides not having paging for drill-down reports) is extracting the execution id from the drill-down HTML content: SSRS set execution id only to image URL links (as far as I know) as part of the query string. This means that if the drill-down report does not have an image then sort and toggle operations will not work.

Once again, our drill down reports have images so this compromise is acceptable for our case.

If you think that this approach will work for you I'll be happy to share code snippets.

Alan, thank you a lot for the great work you have done with this viewer.

@PriyeshOulook

This comment has been minimized.

Copy link

@PriyeshOulook PriyeshOulook commented Jun 10, 2019

@ivancogeorgiev

I am using .net c# programming to view the report from SSRS(.rdl) using WCF based on Alan Juden.
I have used Report Server Commands (rs:) ShowHideToggle as a parameter for drill-out data.
Could you please help me how to use ShowHideToggle parameter into Render method of WCF?

When i tried to toggle the button, the server simply returns an empty response, nothing shown in the response neither data (same “without drilldown” data) nor error.

I am simply clueless about what is happening. I am facing SSRS(.rdl) Drilldown, Sorting and Drillthrough issues for viewing the report.

I think your above approach is work for me, It is really helpful if you share code snippets or any example related to Sorting, DrillDown, Drillthrough which is working at your side based on Alan Juden.

Thanks ivancogeorgiev.

@satishkumar1610

This comment has been minimized.

Copy link

@satishkumar1610 satishkumar1610 commented Nov 18, 2019

We solved the problem with the drill-down by parsing the HTML content and attaching javascript function on each of the drill-down links.
This javascript function sends GET request to the Reporting Server (via our API since we need to set credentials) and fetches the report content in HTML format.
We are aware that with this solution we are losing the paging feature but for our case, this is not very important since the reports are not that large. Drill-down reports are always shown on one page.

For the drill-down reports, we overrode the print and export features of the viewer.

We resolved toggling and sorting for the drill-down reports in a similar way: from the drill-down HTML report content we extract the execution id. This id is required for the Reporting Server to process the sorting/toggling request and return new HTML report content.

The second and last limitation we have (besides not having paging for drill-down reports) is extracting the execution id from the drill-down HTML content: SSRS set execution id only to image URL links (as far as I know) as part of the query string. This means that if the drill-down report does not have an image then sort and toggle operations will not work.

Once again, our drill down reports have images so this compromise is acceptable for our case.

If you think that this approach will work for you I'll be happy to share code snippets.

Alan, thank you a lot for the great work you have done with this viewer.

Hi Ivan,

Great to hear that you resolved the drilldown reports.

I am having the same issue, if you can help me with your code snippet it will be great full.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.