While I am still mostly thrilled with the new reference query functionality I have ran into one major problem. If you try to use a BAQ that references another BAQ as a data source, either in a BAQ report or an RDD report with a BAQ data source, it gives an error about nested queries not being supported. Support can reproduce this but they won’t submit it to development unless I give them detailed steps on how to recreate the baqs (they won’t use the baqs I uploaded to the case and apparently don’t know how to use their own software).
Anybody else tried this and gotten it to work?
Known limitation?
I’ve used the BAQ as a datasource, but only for BAQ dataview/grid use. I hadn’t taken it as far as a report yet. That seems like an unfortunate limitation. Hopefully they get that working.
I don’t think this is a bug. From a technical perspective the way that RDDs are built I can see how this would be difficult to implement.
They’ll probably send you down the ideas route. But note that RDDs can already use multiple BAQs as a data source (even before this function existed) so you can fairly reasonably re-create that in the RDD itself
Not yet, not sure why I need to tell support how to create a baq? It’s really exhausting to have to explain stuff like that. I provided the baqs so if they really need the steps they can just look at the baqs I provided and add the same tables and columns?
No, if BAQs work in BAQ designer, then this part is fine. if you attached them. If no, explain what referenced queries options you used - temp table,
Then explain how report was created.
Maybe you can tell support that. I already explained earlier in the case how I used the baqs to create the report. I tested both RDD report and BAQ report.
Waitaminute is this working in the current production Epicor version? I’ve seen it mentioned a couple of times now in ways that don’t sound like someone’s playing around in a future version preview.
