2517499 - Custom report throws a validation error on import/execution

A custom report that was previously working in b1705 (or a previous version) is now throwing an error on import/execution.

• Error Type A

OR

• Error Type B

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

SAP SuccessFactors Learning

• This is the result of a 1708 enhancement (LRN-17962).
• The enhancement is designed to stop reports running if they contain a design flaw serious enough that allowing it to run may impact general report node performance.

Error Type A

• You never want to bind the main dataset of the report to a column cell. The main dataset returns all rows of data for the report which can be typically huge. The current row of data from the main data set is already available to the column.
• Any dataset bound to the cell gets run over and over again and BIRT puts the results of this dataset into memory, which eventually can cause an out of memory issue on the report node.
• The report's developer will need to amend the affected report so that the Main Dataset is not bound to any Report Columns (see below screengrab for illustration of incorrect column binding)

ERROR TYPE B

• Hidden Tables in reports must now be unhidden to mitigate impact of potential report node performance issue

IMPORTANT:

• Please note custom reports troubleshooting and support are beyond Product Support scope (2706322).
• If further assistance is required, please check the Resources available at 2379690.

 2379690 - Custom Report Development and Support - SAP SuccessFactors Learning

report, custom, failing, validation, error, new, dataset, binding, table, cell, hidden, import, execution, execute , KBA , LOD-SF-LMS-REP , Reporting Data , LOD-SF-LMS , Learning Management System , LOD-SF-LMS-PRD , VJDBC Setup or Connection Issues , Problem