I was really thinking this would be an optional, non default setting per report. Not a default behavior or a YAOUS. I agree that in most situations knowing that the report was run, and that it had no results is useful.
I think than in our use case we just had a situation where having any results was rare for some locations, so it was frustrating to have to check the report again and again.
I like the idea of including the row count in the email. I think that would largely solve the issue. Thanks for that suggestion.
Josh
I was really thinking this would be an optional, non default setting per report. Not a default behavior or a YAOUS. I agree that in most situations knowing that the report was run, and that it had no results is useful.
I think than in our use case we just had a situation where having any results was rare for some locations, so it was frustrating to have to check the report again and again.
I like the idea of including the row count in the email. I think that would largely solve the issue. Thanks for that suggestion.
Josh