Details
-
Type: Bug
-
Status: Done/Fixed
-
Priority: Trivial
-
Resolution: Fixed/Completed
-
Affects Version/s: 4.2.9
-
Fix Version/s: 4.4.0
-
Component/s: None
-
Labels:None
Description
I've been using & recommending 'dummy' DAO's to get past the requirement for a 'dao' param when defining columns for something that doesn't have a dao - but in fact it doesn't need to be a requirement in the report class.
PR handles this not being set gracefully