Item not linked to dataset, and "table1" issue

Hi--

I have a report project in VS (2003). I have a report in that project that was working properly. I copied objects from that report to a new one and created a new dataset for the new report (under it's Data tab). Though both datasets (for each of the reports) seem healthy, i.e., they produce data when run, I am now experiencing the following problems:

1. In both reports, the datasets seem to be unlinked, somehow. I know this by right clicking on a field of the report, going to expressions, then selecting the Fields node. Instead of listing fields, as used to be the case, it now says "Report item not linked to a dataset."

2. If I attempt to preview either of the reports, I get an error that reads, "The table 'table1' refers to an invalid dataset name 'MedMgmt.' MedMgmt is the dataset name of the first report. I changed it to another name, but I still get the same message.

I have clicked and right-clicked everywhere and have not found a way to re-link the dataset to the report. Why Reporting Services can't figure out that the dataset in the report's Data tab is the dataset to link to is a point of deep annoyance, but whatever... If anyone can please help me solve these problems, I would be very grateful! Thank you!

I have exactly the same problem. Only way around it (for me) so far has been to build the report all over and let the wizard link it, then copy the elements 1 by 1 from original... real pain...

There's GOT to be a better way?

|||

I think i know what it is. What is this object you are looking to link? If its a table, List, or Matrix : Right click the object (make sure the whole object is selected and click properties. if properties slides out Scroll down to "Dataset Name", there should be a drop down which all the datasets in your report. Select the one you are grabbing you attributes from. The reason your getting that error is, the object is linked to dataset names from your other report (since you copied them over). So you need to change the dataset names for each object. This is why it shows the name of your dataset from your other report.

IF the properties box opens up for the table/matrix/list , then you should see (3 textboxes down) "Dataset Name". if its empty or has something in it...i would click the dropdown anyways, and make sure the right dataset it selected.

I hope this helps!

Item not linked to dataset, and "table1" issue

Hi--

I have a report project in VS (2003). I have a report in that project that was working properly. I copied objects from that report to a new one and created a new dataset for the new report (under it's Data tab). Though both datasets (for each of the reports) seem healthy, i.e., they produce data when run, I am now experiencing the following problems:

1. In both reports, the datasets seem to be unlinked, somehow. I know this by right clicking on a field of the report, going to expressions, then selecting the Fields node. Instead of listing fields, as used to be the case, it now says "Report item not linked to a dataset."

2. If I attempt to preview either of the reports, I get an error that reads, "The table 'table1' refers to an invalid dataset name 'MedMgmt.' MedMgmt is the dataset name of the first report. I changed it to another name, but I still get the same message.

I have clicked and right-clicked everywhere and have not found a way to re-link the dataset to the report. Why Reporting Services can't figure out that the dataset in the report's Data tab is the dataset to link to is a point of deep annoyance, but whatever... If anyone can please help me solve these problems, I would be very grateful! Thank you!

I have exactly the same problem. Only way around it (for me) so far has been to build the report all over and let the wizard link it, then copy the elements 1 by 1 from original... real pain...

There's GOT to be a better way?

|||

I think i know what it is. What is this object you are looking to link? If its a table, List, or Matrix : Right click the object (make sure the whole object is selected and click properties. if properties slides out Scroll down to "Dataset Name", there should be a drop down which all the datasets in your report. Select the one you are grabbing you attributes from. The reason your getting that error is, the object is linked to dataset names from your other report (since you copied them over). So you need to change the dataset names for each object. This is why it shows the name of your dataset from your other report.

IF the properties box opens up for the table/matrix/list , then you should see (3 textboxes down) "Dataset Name". if its empty or has something in it...i would click the dropdown anyways, and make sure the right dataset it selected.

I hope this helps!

Issue with dataset from stored procedure

I am having an issue with a dataset in SSRS2005. Basically, this is a
simple dataset from a stored procedure, with two char parameters.
I just picked the stored procedure name and let the BI Studio pick all
the default settings. Then I try to preview the data. The BI studio
locks up. This happens every time.
The stored procedure works fine in SSMS. It returns one simple small
data set. It takes 6 seconds to run in SSMS. So I decided to set the
timeout to 30 seconds in the dataset. It times out and gives me the
expected timeout error message. If I set the timeout to 60 seconds, it
locks up - no timeout error message.
If I choose any other similarly structured stored procedure, no
problems occur. So I tried slightly modifying this procedure, but no
luck.
If I watch the procedure in sql profiler, the procedure is started, but
it doesn't complete until I kill BI studio.
Any ideas?hey, scott
when you say you "try to preview the data", do you mean you execute the
query from the data tab in the Report Designer, or do you actually go
to the Preview tab and run the report?
If you mean the latter, then I suggest you take a look at the report
layout, and make sure you're not creating some kind of bottleneck by
doing heavy grouping or formatting.
If you mean the former, I'd encourage you to take a look at the
properties of you data source (shared or in-report) and make sure you
are giving it the correct connection string, and authentication method
(windows/sql/none) and credentials.
Regards,
Thiago Silva
Scott.Stonehouse@.gmail.com wrote:
> I am having an issue with a dataset in SSRS2005. Basically, this is a
> simple dataset from a stored procedure, with two char parameters.
> I just picked the stored procedure name and let the BI Studio pick all
> the default settings. Then I try to preview the data. The BI studio
> locks up. This happens every time.
> The stored procedure works fine in SSMS. It returns one simple small
> data set. It takes 6 seconds to run in SSMS. So I decided to set the
> timeout to 30 seconds in the dataset. It times out and gives me the
> expected timeout error message. If I set the timeout to 60 seconds, it
> locks up - no timeout error message.
> If I choose any other similarly structured stored procedure, no
> problems occur. So I tried slightly modifying this procedure, but no
> luck.
> If I watch the procedure in sql profiler, the procedure is started, but
> it doesn't complete until I kill BI studio.
> Any ideas?|||Sorry, I mean the former. I am doing the preview from the data tab.
I know there is nothing wrong with the connection strings or anything.
I started commenting out fields in the stored procedure, and there are
three fields in particular that appear to be causing the problem.
Again, these look fine when I run it in SSMS. In each of those fields,
I did a coalesce, so I thought maybe that was related, but if I remove
the coalesce, nothing changes.
Then I tried putting the full stored procedure query into the dataset
as text instead of a stored procedure. Everything works. It was cut &
paste, so I know it's the same.
I would just leave it like this, but I have several reports running
from the same procedure. I don't want to have to edit every report
when it's time to make a change to the query.