Is it just me, or does anyone else really hate how they changed the join type from inner join, left outer join, etc to the table names? It takes more of a thought process to create a join than if it were just the standard join types, for me anyway. If you don’t understand what a left outer join is, you probably shouldn’t be making BAQ’s. Would love to be able to turn this off. Anyway, back to your regularly scheduled day.
It’s fine either way for me but I’ve found that my clients finally understand what is happening on the joins now hahaha
On a future release… Maybe add text in brackets indicating their meanings (inner join) for instance…? So all understand clearly…
Maybe they took note of how SSMS shows it in the designer.
This was probably a marketing decision… “inner join” is a technical term, but doesn’t really describe things unless you are technical, at which point, it makes total sense.
But as we know… more and more people are getting into the data query business… all levels of an organization. The new join types are clear and describe what will happen in layman terms.
But to answer your question… I didn’t “Need” this feature, but it sure has made training newbies on how to BAQ much easier.
I’m sorry, I did this renaming because PMs wanted to “humanize” query design process.
But you can still admire old good icons on relation links 
I like this – For Dmitry
We actually brainstormed using images just like every SQL textbook ever written
When you guys change naming conventions like this, do you analyze like Support Cases or Focus Groups to figure out How many people are confused by the terms the techies love? Or is it just lack of backlog items to work on
On second thought it’s not that bad, its self-explanatory.
I must admit it bugged me. It adds a moment of confusion every time because it suddenly isn’t the standard terminology I’ve got so used to.
But I figure those of us who are used to it should be the kind who can adapt, and if a little irritation for me might smooth the way to more people getting the hang of it and taking some of the load off me then it’s probably worth it. So I’ve said nothing until now and I don’t want to add to the grumbles!
Hi @Dmitry_Kashulin In the BAQConstants you can select the WorkStationDescription… but not WorkStationID… Is it possible to add that in the near future? it would help alot =) without it we have to pass in via C# the WorkstationID if we want to join on it to find the Device/Printer…
((Ice.Core.Session)(this.oTrans.Session)).WorkstationID
Where are you WorkstationID…
If you do us this we will continue to give @Bart_Elia a hard time every Monday and Friday 
How do you help people on the Forum… with this change? Just Left JOIN your JobHead on Part… Non-Techie: I don’t see anywhere anything to pick LEFT JOIN, what are you talking about? Is Left Join an Epicor module I must buy?
You have to change your answers to “Match rows from TableA and TableB”
Likewise when they attempt to convert a mini SQL Query to BAQ when SQL states “INNER… JOIN” they knew they had to pick Inner Join at the least they could find the word “JOIN” within the UI somewhere and try to make sense… Like this they won’t know 
That hadn’t occurred to me. I suppose I’ve been assuming people on this forum know enough to translate the standard terms back to the new EpiLanguage, since it takes a certain commitment to get this far. It hasn’t been a problem yet, anyway.