Several InvalidReference Exception when report definition is run
Multiple InvalidReference Exception at the back end when a report definition is run.
Steps to Reproduce
- Add a data type and add a new column
- Create a local data source. This creates a new table
- Create a report definition in the same class including a newly created column
- Run the created report definition
The 'Report on Descendent classes' instances option on the Data Access tab of the Report Definition rule has a new option to include data from all the descendant classes of the report's primary class. If the descendant classes are mapped to multiple class tables, the generated SQL query performs UNIONs to include this data. Previously, only a single class was included in the report.
ResolutionPerform the following local-change:
Open the report definition Data Access tab and disable the 'Report on Descendent classes' check box.
0% found this useful