On Friday, it’s EpiUsers Frideas Day! Have you been to the Epicor Ideas Portal recently? If so, are there some ideas you want to encourage other users to vote for? Maybe want to add comments to an existing idea?
KIN-I-5419 - Create a VS Code Extension for BPMs / Functions etc.
It goes a long way to that devops Idea but in smaller chunks @Mark_Wonsil maybe some functional decomp will get traction 
This has been requested many times - users don’t want to have to keep selecting the same options every single day in time phase. It should just stick.
https://epicor.ideas.aha.io/ideas/KIN-I-5397
Sorry, your 
's are cracking me up!
Just made this one. https://epicor.ideas.aha.io/ideas/FRM-I-6
It’s hard to explain in words; just look at the picture. I want the subquery name in a column on the right-side grid.
EDIT: This is a tangent I suppose, but have you ever added the same subquery twice to your top-level query and added the same calculated field from both to the top-level and it appends a 01 to the second one? I think this is a symptom of this same design, that the UI can’t distinguish between the calculated fields. And I hardly can either at that point - you have to make a mental note of what SQ instance spawned Calculated_MyField01. OR you make ANOTHER calculated field that is just equal to that instead…
Also this one from @TyrusRechs :
We need a new way to access log files in a cloud environment
See my comment and pic there (from this week) if you want an example of the frustration. (And I’m on prem!)
Is that Ellen DeGeneres?
Handy
I miss the dinosaur ride.
Technically you see it in the tab name:
and all display fields are for that subquery. Suggested column would contain one name only
That tells you where you are, but not where the field in the selection came from.
It’s a problem in classic too.
Exactly.
You have a subquery named OrderDtl with a Summarized calc field to total the order value.
If you name the calc field OrderDtlTotalOrder and the field label as TotalOrder this would give you the trace logic back to the correct subquery.
Wouldn’t that work?
I assume it is only relevant for calc fields? All other are not a problem?
I am not sure it is a good idea to add a column for all fields then…
Well, a few things.
First, sure, there are always ways around it. I named some others earlier.
Second, I mean, why not make the system easier to read and debug? I guess it’s heresy, but I don’t always have a grand plan when making a BAQ - the design typically evolves as I get into the weeds and realize I need 5 subqueries when I thought 1 would do it (for example, the BAQ in the pic I shared is like that). Well, now my original simple naming convention is hurting me, yes that’s true.
Third, try your trick with the same field twice, from two instances of the same subquery. That’s when you get the 01 thing I mentioned earlier.
That was my first thought, but then I thought a little bit more, and I think not.
We reference the same fields and tables sometimes in multiple subqueries.
Pro: Having an indicator would be super nice.
Con: Gonna make field names longer and more cumbersome.
…unless some other indicator, like just another column with the name shows up… 
But you cannot have the same table id and alias will be different in different subqueries, like Customer_CustNum, Customer1_CustNum
Only calculated is a special table name and alias prefix
Yes and no.
The grid displays Table_Field.
So imagine I use EntityGLC in 3 subqueries (one is named EntityGLC1, another is EntityGLC2 etc.).
Yes, EntityGLC1 is only used in one place, so, yes, IF I remember that EntityGLC1 was the one I used in the PartGL subquery, then I can trace it back. But I have to remember that.
This is a pic of the sidebar in the calculated field editor. It’s fine (if narrow!). I’m just using it to illustrate the grid problem.
WAY out of the box thought… but what if each query/subquery had a color associated to it. So the font color of the field(s) would represent what query they came from? Purely visual, would avoid any column naming scheme issues.
Kind of like in AutoCad where you assign a color to a layer… then you can tell what artifacts on your Cad drawing came from each.
