Most annoying thing in EPICOR… Read through a few existing “Your topic is similar to…”, but to no avail.
I have a BAQ
where I added the Part.Specification to the Displayed Fields. Saved and ran BAQ successfully. I then opened the SSRS report, went to
and updated the query to
=“SELECT [Part_PartNum],[Part_SearchWord],[Calculated_TodayDate],[Calculated_CurrentSite],[Calculated_PrintNSF],[Calculated_CustomPart],[Calculated_ItemNum],[Calculated_PartNum_BC],[CustXPrt_XPartNum],[Customer_CustID],[Customer_Name],[UD40_Key5],[Part_ClassID],[Part_PartDescription],[Part_Specification] FROM dbo.[BAQReportResult_” + Parameters!TableGuid.Value + “]”
I then added the Query field as instructed in other articles. (Does it matter if query field was added before changing actual query?).
Running report gives the following error:
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: Invalid column name ‘Part_Specification’.
I thought that was taboo?? Every post says not to do that since it creates more problems. Also, changing the sql select statement and adding the field is supposed to be the same as the sync dataset… I thought.
I have only ever done it to BAQ’s and reports I have built and maintain. So far I haven’t run into any issues when that is the case. I wouldn’t do it to anything outside of that.
One thing you can check is if you see the updated fields in your report data definition that is found on your report style for this BAQ report. If they aren’t in the report data definition (RDD) then I don’t think they are going to be generated for the report dataset and therefore the SQL query is going to return nothing for those fields.
hi Utah,
I went to the RDD, but I don’t see anything. Everything is “grayed” out. Am I supposed to export it, make changes, and reimport it… OR something like that.
So I found KB0029573 and followed the instructions for 10.2. I was able to go to the BAQ Rpt Designer and call up the BAQ report.
I then went to Rpt Style Maint, clicked on “Sync Dataset”, went to Action menu and selected Download SSRS report.
I went into Report Builder and updated the report that was downloaded.
I went back to the BAQ Rpt Designer, Action Menu, Upload SSRS Report… and received the following error message:
Now I know the file is there. Here is the screenshot:
Hi Kevin, I have looked at the path in the error message and the path in the File Explorer screenshots a few times. Where is the difference between them? Just not seeing it…
Ok. So I saved the .RDL file on my desktop as you saw in File Explorer. I have the SSRS report that I downloaded from the server. Here is the Report Style
When I try to upload from BAQ Report Designer, it adds the extra reports/CustomReports. I gather it is getting it from the Report Style. The Report Style worked before I added the field Part.Specification. Should I change the “Report Location”? This is where it resides on the server. Also, I get an error that filepaths cannot exceed 260 characters. Should I just move the ProdLbl-Etables.RDL to the C:\ Temp folder? More complicated than it needs to be I’m sure…
Went to test report, received following error:
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 ‘RptLabels’. —> System.Data.SqlClient.SqlException: Invalid column name ‘Part_Specification’.
(There is a lot more, but I think the above says it all).
You originally said you “did the same thing for RptLabels”. I would go back and undo that. Take the Part_Specification field out of that query. You probably don’t use the RptLabels dataset, so I wouldn’t bother updating it.
Open the same Report ID in Report Style. Look at the “Report Location” field on the Styles > Style Detail > Detail tab. Methinks there is a typo in this field. You can see from your posted error message that it thinks the file is in temp\reports\customreports… yadda-yaddah. Just verify the path that should be here based on where the rdl file is sitting on your PC. Update this to match, then try the upload again.
Edit: Yeah - What @klincecum said!
We’ve faced same issue with STANDARD reports and those issues were resolved by either of following
. Removing the RDL.DATA file and re-build the project and re-upload RDL file via RDD screen
. Uploaded RDL file was from their solution and not the ones from BIN folder
. Delete the RDL file from SSRS Server and Re-Upload it via RDD screen
