Classic - Not able to export the records to Excel beyond 6000+ rows when a parameterized lookup attribute is incudes as a column.
Article ID: 272766
Updated On:
Products
Issue/Introduction
You are in classic and are trying to export the data from a Portlet.
When you try to export the records using (Export to Excel( Data only)), The records are not getting exported even after 15 minutes of loading.
This only happens when there are more than 6000+ rows and a parameterized lookup is included as one of the columns.
Environment
Release : 16.0.1, 16.1.1, 16.1.3
Cause
When an export is run, the value for the parameterized lookup column must be resolved. The parameterized lookup query will run for EACH and EVERY row.
The result is a query that includes thousands of parameters. This can exceed the Oracle or MS SQL limit for the number of parameters allowed in a query.
Resolution
This is a database limitation with Oracle and SQL Server.
Define a static lookup if possible to replace the parameterized lookup.
Alternatively, create a new text attribute. Define a process to trigger when the parameterized lookup is updated. The process should contain a GEL script to take the value from the parameterized lookup and put it into the new text attribute.
In your portlet, include the new attribute to replace the parameterized lookup column.
Additional Information
Feedback
