It would be great if the developer (via property on Page and/or PageExt for one or more pages) or the admin (via NST configuration for all environment) can hide or disable the "Search" field on lists.
I'm asking this because on very long lists if the users use this function trigger heavy SQL query that (if the number of records/columns are very big) gives users the error "Searching for rows took too long and was stopped. Try to search or filter using different criteria."
Comments
Alternative could be for user to specify which field(s) the searvh should be conducted on.As for now the search if to far too broad. Doesn't work well!
Category: Development
This does not make sense for a developer option as most ledger pages are affected. Microsoft needs to determine whether searches make sense on ledger pages versus master lists. Same is true when turning Analyze on for many list pages.Rather than go into what looks like a freeze, a warning that at times filtering is a better option than Search would be informative.Could then make a case that a warning based on numbers of records involved is helpful to inform the user, or default search to page contents only may be kinder
Category: Development
@Business Central Team can you please review this idea again? Because on large tables the search function is a silent performance killer.
Category: Development
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team