Can someone explain this disclaimer. Has there been problems where this message was needed?
bahahah what version is that on? I’ve never seen this before.
Im on 10.1.400.5
I think it came out on 10.1.400
10.2.xxx not 10.1
ah must be new.
My guess is people complain cause they copy and paste that “query” and it doesn’t work.
1 Like
Its shows up on all the BAQs, new and old
Can this disclaimer be removed or is this standard in all new BAQs?
Its standard - why do you want it removed?
Don’t worry, once users get used to it, it will be ignored, just like all other Epicor documentation… 
3 Likes
Does it impact anything else? Why did it all of a sudden show up and does it show up in Live and everywhere else? I mean, this is a real query being executed so why the disclaimer? Maybe it’s just more annoying to the customer or if they are actually trying to make sense of what the disclaimer is actually saying.
The disclaimer says that it is not the real query being executed.
My guess is that people copy/pasted it into SSMS and it doesn’t just work, and they got sick of answering calls about it. Plus the BAQ system also runs security into the fold, so it really isn’t the same as what’s being executed.
Why would it not be a real query even when I created a new BAQ? New BAQs are not copied over so why would it still be displayed in new BAQs?
After thinking it through, I probably was one of those people that actually tried copying it into SSMS so it makes sense with the disclaimer. Probably confusing to the end user when creating new BAQs.
That disclaimer really is laughable… it’s almost like, ok do not actually think you can trust the data that this thing you built pulls because it’s not real. 
It depends on your definition of “real” I suppose. It is what is being done in the BAQ, it’s just not what’s being done against the server when it runs. I code lingo, they call that abstraction, which basically means, they give you a way to do something without having to know everything that’s done under the hood. That’s really what the BAQ editor is doing, even though it’s pretty close to native SQL, it isn’t 100% the same.
3 Likes
I agree that the disclaimer could have been written more clearly though. I think it would be better if it just dropped the “Not a real query”. Maybe something like this
Disclaimer: This is a simplified version of the query and does not represent the exact SQL produced on the server.
3 Likes
Just noticed it on all of my baq in 10.2.400.12 lol freaked me out lol
I did not see that in the patch notes lol
So it is not saying the data isn’t real, what it is telling you is that the SQL that you see will not necessarily produce the same results as the BAQ Execution itself. Particularly because the BAQ has to add the security context such as Company, Plant, Territory, Field Security etc.
So what it does is it gives you the SQL equivalent if you were not accounting for any of those things.
1 Like