We have just upgraded our system from 13.3 to 15.2 and facing issue while extracting data in Export to Excel.
In 15.2 User is trying to extract project list data ( 10-15 columns and 1500 - 2K rows) and while using option Export to excel, after some time Excel file is generating with following message inside -
The system has determined that this export to Excel will take 43.43 minutes to complete, which is greater than the allowed amount of time. The operation has been stopped by the system. Please refer to the online help for more info.
Data with same number of rows, filters and columns is easily being extracted by System administrator with 2-3 mins in 15.2.
When user tried to extract same number of rows, filters and columns in export to excel in 13.3, it is taking 7-9 mins. User has tried to reduce number of columns in 15.2 but still getting same message in generated excel file.
All Parameters are set with default value as follows. Number of rows are not too high and all Columns on list page are in Project properties page and user has view access on it so this should not cause of taking long time.
So Please any suggestions on Why 15.2 system is taking too much time in Export to excel? Is there any config is missed out while upgrading to 15.2?
You may want to trace to find out where the time is spent so much. Also check what is the Attribute Value Protection Setting you have on the list pages
Also what was the time taken in 13.3 for the same export?
Same setting in both 13.3 and 15.2
Same export is taking 7-9 mins in 13.3.
Now the only way to see how long it takes to read the data from database in both 13.3 and 15.2 and compare both.
But We can't login in DB with user accounts who are facing this issue. No measurable difference with my account in DB. It surprising me that only 2k rows is taking too much time or 15.2 system who is calculating time for export to excel is using wrong method.
Any suggestion on this query........
We already have a case and we will work with you on that and provide the information/fixes based on the investigation done via case.
Did this issue get resolved? What is the fix?
No fix. Ca guys are not able to identify the cause and fix this issue. Not even Bug raised for this.