Report Viewer Sort and Drill Through

We have the ReportViewer placed inside a DotNetNuke framework which is
displaying the initial report fine. However if we create a sort link on any
table header name or create a link on some data returned for a drill though
the new report renders outside the Iframe, outside the framework, and renders
as if you had called a URL report.
Is there any solution for a link within the report viewer Iframe that will
render to the iframe?
Anything would help,
Thank you,I had the same problem as you, sort of.
The solution is to modify the ReportViewer control. In the Render method,
assign a name to your IFrame.
output.WriteAttribute("name", "reportFrame");
On the BuildUrlString() add the rc:LinkTarget device info to point to your
IFrame.
this._url = this._serverUrl + "?" + this._reportPath +
"&rs:Command=Render&rc:LinkTarget=reportFrame" +
this.EmumProperties(this._properties);
Hope this helps.
Marlon
"Dan Costello breadbelt.com" <Dan Costello
breadbelt.com@.discussions.microsoft.com> wrote in message
news:EAA4C2DE-FDF3-4D45-B044-37BC7FA2700A@.microsoft.com...
> We have the ReportViewer placed inside a DotNetNuke framework which is
> displaying the initial report fine. However if we create a sort link on
> any
> table header name or create a link on some data returned for a drill
> though
> the new report renders outside the Iframe, outside the framework, and
> renders
> as if you had called a URL report.
> Is there any solution for a link within the report viewer Iframe that will
> render to the iframe?
> Anything would help,
> Thank you,
>|||Thank you for the code this helps and gets me closer but still has a problem.
The drill through works fine and the FIRST time I sort a column works great.
However, the second sort in the same iframe seems to loose the iframe
identifier therefore rendering outside as if it was a URL rendered report as
before. Any suggestions?
Thank you again, we are a step closer!
"TechnoSpyke" wrote:
> I had the same problem as you, sort of.
> The solution is to modify the ReportViewer control. In the Render method,
> assign a name to your IFrame.
> output.WriteAttribute("name", "reportFrame");
> On the BuildUrlString() add the rc:LinkTarget device info to point to your
> IFrame.
> this._url = this._serverUrl + "?" + this._reportPath +
> "&rs:Command=Render&rc:LinkTarget=reportFrame" +
> this.EmumProperties(this._properties);
> Hope this helps.
> Marlon
> "Dan Costello breadbelt.com" <Dan Costello
> breadbelt.com@.discussions.microsoft.com> wrote in message
> news:EAA4C2DE-FDF3-4D45-B044-37BC7FA2700A@.microsoft.com...
> > We have the ReportViewer placed inside a DotNetNuke framework which is
> > displaying the initial report fine. However if we create a sort link on
> > any
> > table header name or create a link on some data returned for a drill
> > though
> > the new report renders outside the Iframe, outside the framework, and
> > renders
> > as if you had called a URL report.
> >
> > Is there any solution for a link within the report viewer Iframe that will
> > render to the iframe?
> >
> > Anything would help,
> >
> > Thank you,
> >
>
>|||I was testing on a report that had only one level of drill-through, so I
never had the problem before, as the new report would always show on the
dessignated IFrame.
However, on a new report, with multiple levels of drill-throughs, I am now
faced with the same problem as you. The first level would still show on the
IFrame, but the second would always show on _top.
I'm trying to fix this and will surely let you know if a solution comes up.
If you do find a solution, I would really appreciate if you could post it
too.
Thank you.
Marlon
"Dan Costello breadbelt.com" <Dan Costello
breadbelt.com@.discussions.microsoft.com> wrote in message
news:2D8961A7-2606-4341-A177-34249E1948D3@.microsoft.com...
> Thank you for the code this helps and gets me closer but still has a
> problem.
> The drill through works fine and the FIRST time I sort a column works
> great.
> However, the second sort in the same iframe seems to loose the iframe
> identifier therefore rendering outside as if it was a URL rendered report
> as
> before. Any suggestions?
> Thank you again, we are a step closer!
>
> "TechnoSpyke" wrote:
>> I had the same problem as you, sort of.
>> The solution is to modify the ReportViewer control. In the Render
>> method,
>> assign a name to your IFrame.
>> output.WriteAttribute("name", "reportFrame");
>> On the BuildUrlString() add the rc:LinkTarget device info to point to
>> your
>> IFrame.
>> this._url = this._serverUrl + "?" + this._reportPath +
>> "&rs:Command=Render&rc:LinkTarget=reportFrame" +
>> this.EmumProperties(this._properties);
>> Hope this helps.
>> Marlon
>> "Dan Costello breadbelt.com" <Dan Costello
>> breadbelt.com@.discussions.microsoft.com> wrote in message
>> news:EAA4C2DE-FDF3-4D45-B044-37BC7FA2700A@.microsoft.com...
>> > We have the ReportViewer placed inside a DotNetNuke framework which is
>> > displaying the initial report fine. However if we create a sort link
>> > on
>> > any
>> > table header name or create a link on some data returned for a drill
>> > though
>> > the new report renders outside the Iframe, outside the framework, and
>> > renders
>> > as if you had called a URL report.
>> >
>> > Is there any solution for a link within the report viewer Iframe that
>> > will
>> > render to the iframe?
>> >
>> > Anything would help,
>> >
>> > Thank you,
>> >
>>sql