I’m afraid to ask because we use Linked Tables a LOT in E9 RDDs for our Crystal Reports… …but do Linked Tables no longer work in E10 with SSRS? Or how can I get them to work in my SSRS report? Do I need to add a Report Table now and create a Relationship? It was so nice to just use these Linked Tables without having to bring in a new table and create a new Relationship, etc.
I also noticed that if I remove the BTCustNum Linked Table from my RDD and Re-Sync the Dataset for my report, the Linked Table and Fields do not get removed from my SSRS report. So I have to do some manual clean-up in the SSRS OrderHed Dataset Expression and the Field List. Is there a better way to automatically remove these tables and fields from the SSRS report without having to do manual clean-up every time?
I would have thought that after removing the Linked Table from the RDD and clicking the Sync Dataset button it would write over the Dataset Expression removing the code for the Linked Table and Fields but it doesn’t seem to be working…
Thanks for any helpful suggestions or thoughts you might have on this.
-Heather
I’ve broken reports by pressing the sync dataset button so I avoid it.
I always manually clean up the report (both SQL and field list) but would love to hear of better options.
The links work. Going to start with just making sure you have selected the fields you need. Can you take a screen shot of the Description Fields for the BTCustNum link?
If you ised the Sync Data button, crumble the up the report, “She’d dead, Jim”. When you add a table and the columns in RDD you DON’T need to Sync Data. Just go into your report and add the columns in the report, T1.OrderHed_BTCustNum in your case. When you do a print preview everything melds together.
Re-Do the report. Just blow the one away you did a Sync Data on.
A little snippet in case you can’t see in the image:
, T1.[BTCustNum_Address1], T1.[BTCustNum_Address2], T1.[BTCustNum_Address3], T1.[BTCustNum_BTName], T1.[BTCustNum_City], T1.[BTCustNum_Company], T1.[BTCustNum_CustID], T1.[BTCustNum_FaxNum], T1.[BTCustNum_Name], T1.[BTCustNum_PhoneNum], T1.[BTCustNum_State], T1.[BTCustNum_Zip]
That’s as good as if I would have added it myself, right? Yet I still get the error…
If the code looks right, what am I missing? Maybe there are other sinister things behind the scenes that the Sync Dataset button is doing? Maybe letting the print preview meld everything together is the answer?
I will try to resist pressing that shiny red (blue in our case) button of death, doom, and destruction and start from scratch by looking at the XML/.rdl and adding the columns myself in the report, along with running a print preview to pull everything together. This will be good practice for my newbie SQL skills…I guess I was just hoping for the lazy route. Thank you guys for the suggestions and the warnings! I’ll let you know how it goes…
YAY! Following your guys’ suggestions, I got the BTCustNum Columns to work in my report and I am no longer getting the errors! (And I now know how to edit the .rdl in XML format!) Thanks guys!
Just FYI: I did try starting over from scratch with the base SOForm report and using the Sync Dataset button (just curious to see in comparison what the XML looked like…) and it did work…I must have just made so many changes and pushed that Sync Dataset button so many times that I screwed something up. Which is kind of scary and I now understand what you mean when you say you’ve broken reports by pressing that button. So I’ll stick with this manual way to bring in the Columns for now and I would advise, just from my own experience, either not using the Sync Dataset button or using it with EXTREME caution!
…but do Linked Tables no longer work in E10 with SSRS? Or how can I get them to work in my SSRS report? Do I need to add a Report Table now and create a Relationship? It was so nice to just use these Linked Tables without having to bring in a new table and create a new Relationship, etc.
and start from scratch by looking at the XML/.rdl and adding the columns myself in the report, along with running a print preview to pull everything together. This will be good practice for my newbie SQL skills…I guess I was just hoping for the lazy route. Thank you guys for the suggestions and the warnings! I’ll let you know how it goes…
