Hello Everyone,
I actually have 6 questions:
1. Why is it that when i create more than one line in the footer of a group
that the report then does not render drill down correctly? I have heard that
this is a bug. Is this true?
2. Why is it that when i create a report with more than 2 groups that drill
down does not work properly?
3. I have a report that has 2 groupings with 1 line in each groups header
and footer section. The drill down works fine in HTML mode but the footer
section of the 2nd internal group does not show on my exported Excel version.
4. In the new version of RS (2005) will i be able to create a report and
have it render on a server with RS 2000 installed?
5. Will RS 2005 integrate into Visual Studio 2005.
6. Will RS 2005 be ready by early November 2005 like everyone says?
To me 1, 2, and 3 above are show stoppers for me using RS in a production
environment...
Thanks for any answers that anyone might give.
CoreyI don't know about 1,2,3. I suggest trying it out in 2005 and see if it
still happens.
RS 2005 reports require RS 2005. A 2005 report can not be used with 2000.
However, you can use a 2000 SQL database as the object/metadata store.
RS 2005 comes with a version of VS 2005 to develop reports (do not requre
purchasing VS). If you have VS 2005 it will integrate with it. The new
controls come with VS 2005.
My confidence level is high that it will be released by early November.
Whether you can get it or not depends on how you plan on getting the
product. If you have MSDN and can download it then yes. If you need shrink
wrap then it will be longer. Early November is what is called RTM (Released
to Manufacturing). To make it available for MSDN download takes very little
extra time, to have shrink wrap available takes longer.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"CoreyMas" <CoreyMas@.discussions.microsoft.com> wrote in message
news:8F4B9BB7-6592-4321-9E0F-CC47E21E9BE2@.microsoft.com...
> Hello Everyone,
> I actually have 6 questions:
> 1. Why is it that when i create more than one line in the footer of a
> group
> that the report then does not render drill down correctly? I have heard
> that
> this is a bug. Is this true?
> 2. Why is it that when i create a report with more than 2 groups that
> drill
> down does not work properly?
> 3. I have a report that has 2 groupings with 1 line in each groups header
> and footer section. The drill down works fine in HTML mode but the footer
> section of the 2nd internal group does not show on my exported Excel
> version.
> 4. In the new version of RS (2005) will i be able to create a report and
> have it render on a server with RS 2000 installed?
> 5. Will RS 2005 integrate into Visual Studio 2005.
> 6. Will RS 2005 be ready by early November 2005 like everyone says?
> To me 1, 2, and 3 above are show stoppers for me using RS in a production
> environment...
> Thanks for any answers that anyone might give.
> Corey|||Thanks Bruce,
Can you tell me if there was a Release Candidate version of RS 2005 that can
be downloaded?
Also i do have access to an MSDN subscription (i work for an online college)
so i will be checking RS 2005 out as soon as it is available.
Corey
"Bruce L-C [MVP]" wrote:
> I don't know about 1,2,3. I suggest trying it out in 2005 and see if it
> still happens.
> RS 2005 reports require RS 2005. A 2005 report can not be used with 2000.
> However, you can use a 2000 SQL database as the object/metadata store.
> RS 2005 comes with a version of VS 2005 to develop reports (do not requre
> purchasing VS). If you have VS 2005 it will integrate with it. The new
> controls come with VS 2005.
> My confidence level is high that it will be released by early November.
> Whether you can get it or not depends on how you plan on getting the
> product. If you have MSDN and can download it then yes. If you need shrink
> wrap then it will be longer. Early November is what is called RTM (Released
> to Manufacturing). To make it available for MSDN download takes very little
> extra time, to have shrink wrap available takes longer.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "CoreyMas" <CoreyMas@.discussions.microsoft.com> wrote in message
> news:8F4B9BB7-6592-4321-9E0F-CC47E21E9BE2@.microsoft.com...
> > Hello Everyone,
> >
> > I actually have 6 questions:
> >
> > 1. Why is it that when i create more than one line in the footer of a
> > group
> > that the report then does not render drill down correctly? I have heard
> > that
> > this is a bug. Is this true?
> >
> > 2. Why is it that when i create a report with more than 2 groups that
> > drill
> > down does not work properly?
> >
> > 3. I have a report that has 2 groupings with 1 line in each groups header
> > and footer section. The drill down works fine in HTML mode but the footer
> > section of the 2nd internal group does not show on my exported Excel
> > version.
> >
> > 4. In the new version of RS (2005) will i be able to create a report and
> > have it render on a server with RS 2000 installed?
> >
> > 5. Will RS 2005 integrate into Visual Studio 2005.
> >
> > 6. Will RS 2005 be ready by early November 2005 like everyone says?
> >
> > To me 1, 2, and 3 above are show stoppers for me using RS in a production
> > environment...
> >
> > Thanks for any answers that anyone might give.
> >
> > Corey
>
>|||The last downloadable is September CTP. There is not and there is no plan
for a release candidate to be out for general consumption (I won't be
getting a RC either).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"CoreyMas" <CoreyMas@.discussions.microsoft.com> wrote in message
news:4FDFB8E6-19AC-455C-A82B-4473AB3B9080@.microsoft.com...
> Thanks Bruce,
> Can you tell me if there was a Release Candidate version of RS 2005 that
> can
> be downloaded?
> Also i do have access to an MSDN subscription (i work for an online
> college)
> so i will be checking RS 2005 out as soon as it is available.
> Corey
> "Bruce L-C [MVP]" wrote:
>> I don't know about 1,2,3. I suggest trying it out in 2005 and see if it
>> still happens.
>> RS 2005 reports require RS 2005. A 2005 report can not be used with 2000.
>> However, you can use a 2000 SQL database as the object/metadata store.
>> RS 2005 comes with a version of VS 2005 to develop reports (do not requre
>> purchasing VS). If you have VS 2005 it will integrate with it. The new
>> controls come with VS 2005.
>> My confidence level is high that it will be released by early November.
>> Whether you can get it or not depends on how you plan on getting the
>> product. If you have MSDN and can download it then yes. If you need
>> shrink
>> wrap then it will be longer. Early November is what is called RTM
>> (Released
>> to Manufacturing). To make it available for MSDN download takes very
>> little
>> extra time, to have shrink wrap available takes longer.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "CoreyMas" <CoreyMas@.discussions.microsoft.com> wrote in message
>> news:8F4B9BB7-6592-4321-9E0F-CC47E21E9BE2@.microsoft.com...
>> > Hello Everyone,
>> >
>> > I actually have 6 questions:
>> >
>> > 1. Why is it that when i create more than one line in the footer of a
>> > group
>> > that the report then does not render drill down correctly? I have
>> > heard
>> > that
>> > this is a bug. Is this true?
>> >
>> > 2. Why is it that when i create a report with more than 2 groups that
>> > drill
>> > down does not work properly?
>> >
>> > 3. I have a report that has 2 groupings with 1 line in each groups
>> > header
>> > and footer section. The drill down works fine in HTML mode but the
>> > footer
>> > section of the 2nd internal group does not show on my exported Excel
>> > version.
>> >
>> > 4. In the new version of RS (2005) will i be able to create a report
>> > and
>> > have it render on a server with RS 2000 installed?
>> >
>> > 5. Will RS 2005 integrate into Visual Studio 2005.
>> >
>> > 6. Will RS 2005 be ready by early November 2005 like everyone says?
>> >
>> > To me 1, 2, and 3 above are show stoppers for me using RS in a
>> > production
>> > environment...
>> >
>> > Thanks for any answers that anyone might give.
>> >
>> > Corey
>>
Showing posts with label drill. Show all posts
Showing posts with label drill. Show all posts
Wednesday, March 28, 2012
Monday, March 26, 2012
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
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
Subscribe to:
Posts (Atom)