I have a report to be run on schedule and delivered by email that I would like to to be sent whether there are any records to return or not. If there are no records to return I would like the email to either say so or be a line on the report saying something like “No Records”.
Wild idea: make a union for the BAQ that has a row stating “no records”. This will force a record always.
Then in your SSRS Report exclude that row and show something fancy if there aren’t any records.
I thought about that, Jason. Then I started to ponder if I can hide the “no records” line in the report when there are records.
Or the primary report could be just a report the number of records - simple in a BAQ. Then have a sub-report to show the actual results. Trouble is you only get one result set with BAQ reports, so the subreport would have to be a direct db connection.
That’s why I’m offering the Union with a fake set of values for each field in the BAQ. The SSRS can hide that record and then the Task agent thinks there is always at least one record. But, the SSRS will show only real records.
Jason’s answer would work, or you could actually create a multi BAQ report as an RDD… You could have one record set with something simple like a count and then the second or main record set would be your report. If you are going to insights this year there will be a class on this very topic.
May 03 - Sunday 08:00 AM - 12:00 PM Advanced SSRS Development via Multi-Result Set BAQs
Add the company table as your primary table and add the companyID to your result set. That should ensure a record is always created.
Is there any other source of information on creating multi-BAQ reports rather than waiting until May?
Or is this a feature of an up-coming version of Epicor E10?
make baq as cross company and valid for all companies and shared, multi-baq report should work. isnt?
Nice @zwilli526 ! I like this as it is much easier.