2333805 - PRD performance when configuring a custom report

When working with custom report, specifically within the report dataset, the performance of PRD appears to be slow and inactive.

SuccessFactors Learning Management System (LMS) - All Supported Versions

The behavior of the designer is working as designed. The problem is that because of the design of the SQL and the data being evaluated the performance is not good.

The designer validates the query in the dataset anytime a change is made. It does this by running the query to validate if it returns an error or not. The only techniques available to avoid this functionality is to use either of the options below

1. Add a hardcoded filter into the SQL at design time to limit the run time of the SQL. This should be placed at the lowest level to ensure the maximum impact. This can be accompanied by changing the setting under the dataset/settings for maximum number of rows to fetch from the datasource.
2. Modify the SQL within an XML editor and skip any validation of the SQL within the designer.

PRD Performance; dataset; Plateau Report Designer; custom report; SQL; , KBA , LOD-SF-LMS-PRD , VJDBC Setup or Connection Issues , LOD-SF-LMS , Learning Management System , Problem