We have a BAQ that hasn’t been run in over a year. It worked fine before but we have since upgraded both our version of Epicor (10.2.500.x => 10.2.700.34) and SQL (2016 to 2019) and now the BAQ returns “Severity: Error, Text: Bad SQL statement.” In reviewing some threads on this forum, it seems that…

It’s in the Subquery criteria for Subquery2: [image] I saw that the FOR XML was in a Where clause inside something called AllIssued, so I looked for that calculated field and saw that the value was coming from Subquery2. I then looked at the criteria since it was in a where clause in the SQL text…

FOR XML in BAQ

Epicor ERP 10

Mark_Wonsil (Mark Wonsil) October 5, 2022, 8:14pm 6

FOR XML PATH versus STRING_AGG - ERP 10 - Epicor User Help Forum (epiusers.help)

Topic		Replies	Views
FOR XML PATH versus STRING_AGG Epicor ERP 10 baq	66	12612	October 28, 2024
BAQ incorrect syntax near 'FOR' Epicor ERP 10 e10	10	2260	December 20, 2022
BAQ - Concatenate results from subquery into one field Epicor ERP 10 baq	7	2129	August 30, 2023
Error while using FOR XML PATH statement Kinetic ERP baq	5	958	April 25, 2023
BAQ Concatenated Rows to Single Field Kinetic ERP baq	11	1291	July 13, 2022

FOR XML in BAQ

Related Topics