When I used to design BAQ reports and schedule them to email out, whenever there was no data (for example, no new orders), the report just . . . wouldn’t go out. But now I have switched to using SSRS BAQ reports and have discovered that even when there is no data an empty report is sent to the user.
It’s not the end of the world but its a little frustrating because there doesn’t seem to any way to control this behavior. I am amused at my own frustration because previously I would always complain that Epicor generated errors instead of an empty report. I don’t understand why the behavior is different for SSRS reports vs. SSRS BAQ reports.
So between this “feature” and the fact that there is no way to preview an SSRS BAQ report (have no option to even design it without first putting it on the menu), I sometimes feel like I would prefer to just use the old BAQ report designer even though Epicor has said SSRS BAQ reports are the future and admittedly for complex reports they are really nice. Anybody else? Any solutions I am missing?
I would guess it’s because the Company or perhaps the RptLabel table is the the top table in the RDD so the data set always returns at least one row.
I vaguely remember this conversation from years ago, but what’s the difference between a BAQ Report and and SSRS BAQ report? Can you only reference a BAQ in Report Data Definiton now?
Yeah maybe that’s it. Its the difference between the BAQ report designer and the Report Data Definition/Report Style screens. Lots more functionality in some ways and less in others. You can still create regular BAQ reports, I’m not sure if they will actually get taken away at some point or not.
I feel ya, it was nice to have one place to look at all “BAQ” reports. Now it’s a bit more cumbersome. I do like --what I believe Epicor calls-- Dynamic Reports but do miss some of old.
Sounds like a bug. The reason I always use the New RDD BAQ Reports is because I can pass in BAQ Parameters to the BAQ, while the old one can’t and does post-filtering.
I wonder if this is on their radar to fix, it should fail with No Records – I am working on a BAQ soon that is meant to be scheduled.
Has anyone submitted this as an issue yet? I’m probably going to submit this issue.
The trouble I am having is I have created a RDD BAQ Report for printing Material ID tag for tagging our inventory. The trouble is if our inventory users print directly to the printer vs print previewing they will end up printing something like 20 tags with no data if they entered the wrong part number. The work around to prevent this is to print preview first, however when you are printing barcodes it is best practice to print directly to the printer vs from a pdf. Printing from a pdf can throw off the scale of the barcode and make it not scan properly. Luckily we are not having any issues with scanning with printing from the pdf.
I would just validate the part exists before allowing them to print. Does not stop them from using an incorrect, but valid part, but would stop blanks.