We have Subqueries that we use in multiple BAQs, but in each BAQ, we’ve been re-writing the Subquery. Is it possible to pull a Subquery into a BAQ, without having to re-write it?
Thanks,
Nolan
We have Subqueries that we use in multiple BAQs, but in each BAQ, we’ve been re-writing the Subquery. Is it possible to pull a Subquery into a BAQ, without having to re-write it?
Thanks,
Nolan
It’s in the Aha ideas portal (https://epicor-manufacturing.ideas.aha.io/ideas/ERP-I-158). It’s showing that it’s in development.
This is a feature a lot of people have wanted for a while.
Hopefully soon!
That’s really disappointing - you should just be able to reference a BAQ in another BAQ just like any other table - not as you said, referencing the subquery of another BAQ. Why is the idea marked in development if its not being developed?
This is a difficult technical problem. The structure of BAQs isn’t really sql
There are a bunch of references you can make in a sub query that can pull from parent query and much more
Believe me I spent a lot of time trying to accomplish so something similar and eventually I had to settle for just copying the subquery around.
One option is to have the subquery run as an independent query and then filter up the results after the fact but that would be really inefficient
Microsoft has solved it since the 90s (Access, SQL) so it feels like a gap that Epicor can’t do it. That aside, what is disappointing to me is that the idea is marked in development when its not. I took my votes away from this idea because I thought Epicor was already doing it. Although Olga deleted her comments for some reason, it sounds like it should be more accurately marked unlikely to implement, not in development. It really undermines confidence in the ideas site.
I believe it is under development.
The feature we just got is copy subquery.
The other one is still WIP
Ok Olga’s previous comment is that it wasn’t under development, maybe I misunderstood.