Export to Excel slow / times out on custom objects, hitting E2E_TIMER limit
search cancel

Export to Excel slow / times out on custom objects, hitting E2E_TIMER limit

book

Article ID: 234409

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Export to Excel slow on a portlet that uses an object data provider where the object is not API enabled. The export is hanging and may time out with message about E2E_TIMER limit and error message that the limit is hit: 
The system has determined that this export to Excel will take xx.xx minutes to complete

This will only happen on custom non API enabled objects

Steps to Reproduce:

  1. Create a custom object that is not API enabled.
  2. Add several lookup attributes to it
  3. Create an instance of the object
  4. Turn on SQL trace.
  5. Go to the list page for the object, Export to Excel (Data Only)
  6. Check the SQL trace log for the action npt.gridExcelExport

In the SQL trace we notice excessive calls to odf.getObjectCodes

Expected Results: The Export to Excel to complete within reasonable time

Actual Results: The Export to Excel takes significantly longer, hangs or times out with The system has determined that this export to Excel will take xx.xx minutes to complete

Environment

15.9.2, 15.9.3, 16.0, 16.0.1

Cause

This is caused by DE64076

Resolution

Engineering addressed the defect as part of DE64043 and is fixed in 16.0.2

Workaround

  1. Go to Administration - Objects - filter for the object
  2. Enable the affected object for API by checking API Enable in its properties and Save

(note enabling for API is not reversible)

Additional Information

This can also happen for Project List export if you have Custom Sub-object's under the Project object. In that case enable API for those Sub-objects as a workaround.