FOR XML PATH versus STRING_AGG

Epicor ERP 10
61

This works for me in BAQ Designer, as advertised, but I can’t call the same BAQ from REST successfully.

I now know all the pitfalls of the Persist flag and to not open the settings again after saving QueryOldCompanySecurity once already. I don’t see that as the problem.

Has anyone else had the REST issue? I have a ticket in with support, and Daniel is doing a great job. But I found this and thought I’d ask here, too.

Sorry this is a year late, but I am just now encountering this as we upgraded last week to 10.2.700.25.

I know. We just need to move to SQL 2017+.

62

Thats a pretty vague description of what’s happening. How is it failing?

63

Well I sure feel stupid. There is no problem here except me.

I fixed the BAQ in Production and was “verifying” it with a Development URL. Once I used the URL (duh), all is well.

I apologize for the confusion.

2 Likes
64

We’ve all been there brother!!

2 Likes