Drill-through report passing credentials

Is it possible to drill through to a report that does not have embeded credentials? Every time I link from a report that requires a sql username and password to run to another report that requires the same permissions, I recieve an error message stating: "One

or more data sources is missing credentials" Is there a way to make RS prompt the end user to re-enter credentials after drilling through to the next report, or to make the credentials entered to access the first report pass through to the second report? The drilling through works perfectally from within visual studio, but fails to work when the report is viewed in IE.Did you ever fix this problem? I am having the same problem. It works fine when run in Visual Studio but then on the server it does not prompt again for the credentials when drilling through to the next report. My email is scriptjunk3@.hotmail.com. If you did fix this or get an answer, please let me know here or at my email. Thank you.

Drill-through report passing credentials

Is it possible to drill through to a report that does not have embeded credentials? Every time I link from a report that requires a sql username and password to run to another report that requires the same permissions, I recieve an error message stating: "One or more data sources is missing credentials" Is there a way to make RS prompt the end user to re-enter credentials after drilling through to the next report, or to make the credentials entered to access the first report pass through to the second report? The drilling through works perfectally from within visual studio, but fails to work when the report is viewed in IE.
Did you ever fix this problem? I am having the same problem. It works fine when run in Visual Studio but then on the server it does not prompt again for the credentials when drilling through to the next report. My email is scriptjunk3@.hotmail.com. If you did fix this or get an answer, please let me know here or at my email. Thank you.

Drill-through report

Hi,
I am trying to set up drill-through reports by passing parameters from
one report to the next.
The first layer works: when the user clicks on the field (the
department in this case) the second report comes up for that
department.
But when I try to pass the same parameter to the third report from a
text box, I get a warning: 'The expression referenced a non-existing
field in the fields collection.' The field is listed in the Fields
list and the text box is referencing it using the aggregate function:
=First(Fields!x_department.Value, "DataSetName")
What am I doing wrong? Thanks for any help you can provide...Is the "DataSetName" a part of the third report?
"Hella" wrote:
> Hi,
> I am trying to set up drill-through reports by passing parameters from
> one report to the next.
> The first layer works: when the user clicks on the field (the
> department in this case) the second report comes up for that
> department.
> But when I try to pass the same parameter to the third report from a
> text box, I get a warning: 'The expression referenced a non-existing
> field in the fields collection.' The field is listed in the Fields
> list and the text box is referencing it using the aggregate function:
> =First(Fields!x_department.Value, "DataSetName")
> What am I doing wrong? Thanks for any help you can provide...
>|||well it's a well known problem.
Insted of using Jump to Report use the Jump to URL.
"Ben Sullins" wrote:
> Is the "DataSetName" a part of the third report?
> "Hella" wrote:
> > Hi,
> >
> > I am trying to set up drill-through reports by passing parameters from
> > one report to the next.
> > The first layer works: when the user clicks on the field (the
> > department in this case) the second report comes up for that
> > department.
> > But when I try to pass the same parameter to the third report from a
> > text box, I get a warning: 'The expression referenced a non-existing
> > field in the fields collection.' The field is listed in the Fields
> > list and the text box is referencing it using the aggregate function:
> > =First(Fields!x_department.Value, "DataSetName")
> >
> > What am I doing wrong? Thanks for any help you can provide...
> >
> >|||Thanks for responding!
I am finally able to try the 'Jump to URL', but the parameter is still
not getting passed.
This is what I have in the URL:
=Globals!ReportServerUrl &
"/Incoming+Types+By+Department/Quarterly+Incoming&Department="+=First(Fields!x_department.Value,
"MonthlyIncoming")
I tried using the Parameter!Department.Value instead of First(Fields!
etc.) but it doesn't work either - (FYI: the report parameter is also
defined in the third report.)
The field x_department is being passed from the parent report (Incoming
Types By Department) to the first child report (Monthly Incoming). It
is the field I am trying to pass to the third report (Quarterly
Incoming.) from the 'Monthly Incoming' report.
Thanks!|||Never mind! it works now.
For whoever might be interested, this is the URL I entered in the Jump
to Url box:
=Globals!ReportServerUrl & "?" & Globals!ReportFolder & "/Quarterly
Incoming" & "&Department="&Parameters!Department.Value
Hella

Drill through works eradically

I've got a report that drills through to itself, passing different parameters when drilling through. The report work flawlessly in development, flawlessly when you call the report server directly via url, but doesn't always drill through correctly when the report is called using the report viewer on web site. I've gone as far as to create a single aspx page web site that only has this report on it and it still doesn't work.

The drill through works about 1/2 of the time when viewing through the report viewer. But the other half of the time it takes you back to a previously visited parameter, instead of the parameter you clicked on.

So a series of clicks might work like this:

Parameter Clicked - Resultant page

A - Correct "A" page
B - Correct "B" page
C - Correct "C" page
D - Incorrectly taken to "B" page.

It seems to be worse if you throw in any click of the back button.

We thought at first it might be a parameter caching issue, but we turned off all caching and even created a time-stamp parameter to force no caching.

Any thoughts are appreciated.

Craig

This ended up being a bug. The report viewer control works as expected in Visual Studio 2005, but when linking back to the same report under Visual Studio 2005 SP1, this bug may appear.

Drill through works eradically

I've got a report that drills through to itself, passing different parameters when drilling through. The report work flawlessly in development, flawlessly when you call the report server directly via url, but doesn't always drill through correctly when the report is called using the report viewer on web site. I've gone as far as to create a single aspx page web site that only has this report on it and it still doesn't work.

The drill through works about 1/2 of the time when viewing through the report viewer. But the other half of the time it takes you back to a previously visited parameter, instead of the parameter you clicked on.

So a series of clicks might work like this:

Parameter Clicked - Resultant page

A - Correct "A" page
B - Correct "B" page
C - Correct "C" page
D - Incorrectly taken to "B" page.

It seems to be worse if you throw in any click of the back button.

We thought at first it might be a parameter caching issue, but we turned off all caching and even created a time-stamp parameter to force no caching.

Any thoughts are appreciated.

Craig

This ended up being a bug. The report viewer control works as expected in Visual Studio 2005, but when linking back to the same report under Visual Studio 2005 SP1, this bug may appear.

Drill Through Report -- Passing Date Parameters -- resulting in rsReportParameterTypeMismatch

All,

I have two reports. One is the main/summary report and other one is drill through. When I pass the Start and End Date parameters from main to the drill, the original format of DateTime changes. For example, in main report the data is displayed for following date range:

4/7/2007 - 5/9/2007 (i.e 4 July 2007 to 5 Sept 2007)

which displays correct data.

However, when I click on the drill through link, it jumps to the drill through report but displays data for the following period:

7/4/2007 - 9/5/2007 (i.e. 7 Apr 2007 to 9 May 2007)

The reporting services is converting the value from one format to another of the report parameters when passing them from parent report to the drill through. When run individually, these two reports display data for correct date range. And you can imagine, the child report crashes with rsReportParameterTypeMismatch error if the start or end date had a day part greater than 12 (e.g 25/4/2007).

I can't understand what could be going wrong. All the parameters in both reports are datetime, so intrisically, it shouldn't matter even if the reporting services is converting or using different date formats as long as the data type remains the same. Is there a way to fix this and force the parameters to stay in the format they are provided in the main report?

Your help is much appreciated.

Thanks.

Moved to Reporting Services forum.|||I thought I had posted it in SSRS forum? Anyways thanks.|||

People from Microsoft...Would you mind explaining this so very prevalent and confusing issue of Date time formatting? How to get around this issue of reporting services converting the date time to US format?

Just like the below post, I am using Canadian english as the regional settings. In the following post, someone says similar to what I am suggesting, Why does it matter when the datatype being used is DateTime all along and not string, then there shouldn't be any formatting issues? But the SSRS throws an error anyway.

http://www.eggheadcafe.com/forumarchives/SQLServerreportingsvcs/Jan2006/post25361489.asp

If someone has a solution to this, please advise.

|||

I found a related post discussing a similar issue:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=255248&SiteID=1

I think the reply by Lukasz P. in that thread may be the solution. Has any one tried it?