Has anyone come across a way to use the output of one BAQ as input to another, distinct BAQ? Maybe a “permanent” subquery or some such animal? Any thoughts? Thanks!
When you say “as the input”, do you mean the results of the first BAQ is the data that the 2nd BAQ will work on?
Or that some result is used as a parameter of the 2nd BAQ? Like if the first BAQ derives data range (a first_date and last_date value), then the second BAQ uses those two as paramaters.
I want to use three fields from the first BAQ - part number and two calculated fields. The second BAQ would link part number supplied from BAQ 1 to the PartWhse table and retrieve a couple additional fields from PartWhse.
You could make A BAQ with an inner subquery. That effectively makes a data set that your top level query can link to like any other table. In this setup your first BAQ would be the inner Sub Query (say we name it isq1), and the 2nd would be the top level (say we name it tlq). You’d then put isq1 in the top level and relate to other tables in the top level.
2 Likes
Vote for it on Epicor Ideas. It’s a popular one.
Easily done with a CTE. I recommend that route.