3613770 - [Master KBA] Error Rendering List Report Component

This is caused when a calculated formula is using a divide operation, with denominator leading to 0.

Though the error message in the front end is  generic, the internal logs, accessible by Support, will display the said error.

Delete all the Calculated columns (or) the ones with Divide operation and Preview the output. 

• If data appears without the calculated column, this is the scenario.
• If the error continues to persist, even without Calculated columns, the issue is with one of the below scenarios.

• Add a static/ Run-time filter to exclude 'zero' values for the affected calculated column (e.g.: Field not equal to 0)
  (or)
• A good practice while creating calculated columns with division, is to include a condition to avoid divide by zero.

Imported reports having validation issue.

(OR)

Metadata changes were performed, leading to validation errors in existing canvas reports. 

(OR)

Validation tool displaying error "Failed to deserialize the xml for the query"

1. Edit the Canvas report
2. In the Left bottom pane, click 'Validate Page'
3. Unselect 'Group Errors' checkbox
4. Click 'Validate'

2357604

2357821 

3303827

When a user lacks permission to certain fields, selected in the query, it might lead to either
"Role Based Permission prevents viewing of this component"

or
"Error Rendering list report component"

If the user has edit access to Canvas reports, then navigate to Edit Query and look at each field selected in the query. The one lacking permission would be greyed out.

• Provide permission to the greyed-out field.
  (or)
• Use the 'Check Tool' specified in the adjoining KBA
  (or)
• Manually check for all fields used in the query and verify if User has permission to all the fields in RBP

2326069

2857327

See if any widget takes more than 5 mins to load.

The report's run time depends on multiple parameters. Examples:

• Number of columns and rows (amount of data)
• Cell level permissions
• User’s target population
• Server load

Kindly review the design and RBP of the user and work on query/RBP optimization. 

In most scenarios, filtering the data to fetch for a specific country/BU/Division/Department might help.

When creating an Advanced Reporting query, the drop down shows 'No Realm is available'. And this impacts all Existing Canvas reports leading them to 'Error Rendering List Report Component'.

Issue might be caused due to incorrect back-end configuration:

1. The Advanced Reporting company was not created automatically in the Analytics backend, or its setup is not correct.
2. The Advanced Reporting is enabled but Employee Central is not configured > The Advanced Reporting is a feature within SuccessFactors that allows users to query Employee Central data. If Employee Central is not configured the Advanced Reporting will not work.
3. Schema or dbpool name is incorrect in backend.
4. This error happens after instance refreshes.
   Advanced reporting must be manually refreshed by the support team after an instance refresh.

When a filter is set based on the Picklist label, and the report is being run in a different language than that of the 'Picklist label', the Report will fail as it cannot compare strings of 2 different languages. 

Set a filter on Picklist Codes, which are consistent across languages.