I have an SSRS report that runs with BAQ as its datasource. I added 2 fields to the BAQ from an existing table (Part.PartDescription, Part.PartClassID). I copied the SSRS report ProdIDlbl to ProdIDlbl-Etables. In the report, I added the 2 fields
I am getting the following error when running the report:
Program Ice.Services.Lib.RunTask raised an unexpected exception with the following message: RunTask:
System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: An error has occurred during report processing. ā> Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. ā> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for dataset āBAQReportResultā. ā> System.Data.SqlClient.SqlException: Could not find stored procedure āSELECT * FROM dbo.BAQReportResult_8e918ca008dc453fafa4a870a0735d55ā.
Is this because I changed the BAQ? Do I need to do something to tell the report the BAQ has been updated? The other report Style, Standard - SSRS, which uses same BAQ, still works fine.
Please advise. What else can I provide to help with this issue?
From the Report Style, thereās an option to āSynchronize the Datasetā on the Actions menu. That will do what I said above for you. Iād definitely back up your RDL before doing this. Itās been a bit buggy in the past, so I usually just do it manually.
To do it manually, you need to add the fields to the SQL query. It looks like you added the fields to the report, but those fields on the report have to refer to a field in the SQL Query that drives the report. Right click on the Dataset (BAQReportResult), go into the Dataset Properties. Thereās two items in the tree view that youāll want to understand:
Query: hereās where the query is defined. If you click the Function button next to the big white space that holds the query (should say inside that white box, you can see the SQL query that drives the report. Youāll need to add your field that you added to the database.
Fields: this is a list of all the fields in your report. The āField Nameā is what you refer to in the RDL. The āField Sourceā is coming from the SQL query. These are typically the same thing, but they donāt need to be.
The problem is you added the āField Nameā, but the āField Sourceā is not defined in the SQL query.
I had looked at the Query for the report in the dataset properties, but this is what I saw: =āSELECT * FROM dbo.[BAQReportResult_ā + Parameters!TableGuid.Value + ā]ā.
I have worked with reports where I see and modify the full SQL statement. Thus, I was unsure where to go in this case.
Can it be the fact that the BAQ, being the source of the dataset for the original report, and the report name changing as a result of copying are disconnected?
Should I create a copy of the original BAQ, modify it with new fields, and then create report from that? OR just put that new BAQ as the data definition in the Prodlbl-Etables report style?
Good News! I followed my plan and created the new BAQ from the original. I then created the SSRS report using the BAQ report designer. I updated the report style to reflect these changes. The challenge was being new to creating SSRS reports. Some research and few youtubes did the trick. Once I created the Tablix / Rectangle / textboxes / images, I was good to go. The final challenge always seems to be the sizing of labels. All good now.
