Add Date filter to Global Change Process Status List
This data list consistently returns the error "Unable to load data list. The datalist e77da71d-0a01-4313-9b79-720e82593a49 returned 223735 rows exceeding the error threshold of 100000 as configured in web.config via the DataListRowCountGovenorMaxRowError AppSetting value. The use of this datalist should be changed so that a filter is applied to restrict the number of rows returned by the datalist." Yet the only filter provided is on Status, and even it doesn't work - giving the same error.
-
David Wanless
- Mar 31 2019
- Reviewed: Voting Open
| Organization Name (Please enter full organization name) | The Wilderness Society Ltd |
| Reported Version | 4.0 |
-
Apr 5, 2019
Admin response
To avoid encountering the The datalist <GUID> returned <####> rows exceeding the error threshold, the global change History should be regularly cleared of old entries. The data from the list can be exported if required. Should additional filters be required, this can be achieved via a customisation.
UPDATE: Please create a support case for the data list threshold error and we will investigate solutions. I have updated the Idea title to refer to adding a date filter to the Global Change Process Status List as this is more appropriate for this forum. Errors and suspected bugs should be raised with support.
Related ideas
Thanks Admin. How do we clear the History for this one process other than laboriously deleting individual entries (which we couldn't even do at the moment because the Data List won't load)? We also can't export the data, for the same reason. Yes, customisation could achieve additional filters, but what we're asking for is an additional filter on date (e.g., greater than or equal to or between), as part of the base product so that all organisations benefit from it and no-one has to pay for the whole of it.
Additional info: The filter provided does work for 'Did not finish' but fails for 'Completed' so we can't see from this Data List what has been happening recently. The workaround has been to use Administration/Business Processes/History which has better filters.