In Epicor Kinetic Browser Version , while developing complex BAQ’s and running them getting error “Bad SQL Statement. Review Server Event Logs for Detail”
As we know this a common error in BAQ which arise due to syntax error in the BAQ query. In E10 or E9 , we will review these errors in application server logs or even in database, we will run the same BAQ query in SQL and will find out the syntax error.
Since there is no DB access or application server in E11, where we can find and fix these kind of issues which arises from BAQ??
That’s only true for cloud customers. Access that is. There is still an application server.
But even so, you can just work the problem on the front side breaking down the issues to narrow it down. While it’s nice to have the event log, you can still find the problems without it. I rarely look at that for BAQ issues.
We are working in Cloud Version Only. For Cloud Customers, do we have any option to view this error since this error clearly says “Please Review the Server Event Logs for Details”
Need to know where can we find Server Event Logs??
Usually BAD SQL Statement is what you get when you test the query. Clicking the Analyze button will, most of the time, reveal the actual error.
If Analyze says it’s okay, but the Test is failing, the vast majority of the time is conflict in type that wasn’t caught until runtime. You have a numeric field declared in the query and it turns out the actual data is alphanumeric.
Like @Banderson said, you can request the event logs from support. But they will make you wish you hadn’t asked. Your time will be better spent finding that mis-cast type, or divide by zero error.
As a general rule, whenever I’m doing division I just add something like 0.000001 to the denominator. You won’t get a div/0 error, but you’ll still see where the zeros were because you’re now multiplying the numerator by 100K.
@jtownsend I think I stole that trick from you! It is devious though, if you forget it is there it can really throw off your calculations. At least it lets the BAQ run. I think there was an idea kicking around to allow cloud users to see the server logs, but I am not sure if it went anywhere.
As others have said create a support case with us and provide the data , time, time zone when you received the error and we can create a cloud task to get the cloud server logs for you.
As for the divided by zero error you can also create a case statement in your calculation, for example:
case
when JobMtl.IssuedQty = 0 then 0
else JobMtl.RequiredQty / JobMtl.IssuedQty
end
When it’s better for the math to fail than return numerator / 0.00000001:
numerator / nullif(denominator, 0) to the rescue, because anything divided by null returns null. Also it’s quicker to type than a case statement and I’m lazy.
