The modern search does not do what is required in every case and the legacy search is slow for large datasets. We have no control over what is happening when a user searches a list page.
Please create a new Trigger on the page like:
OnAfterEnterSearchText(var SearchText): boolean
This would allow a developer to subscribe to this trigger and either modify the text entered and return true to allow the standard search to work or it would allow the developer to apply their own filtering and return false to tell the system to ignore the entry.
This would allow me to program a change for users that want the convenience of searching using the search box but want the results to be a specific filtering (like add wildcards to the entered text and set a filter on the Description field), etc.
Comments
Actually it should probably be an event that I can use to modify behaviour of a standard page.The problem with an event is that multiple extension developers may want to take control of the search behaviour and may have conflicting solutions. How about you just let us stick a custom control in the place of the Search box. Ideally we then just need the ability to add a control where the Searchbox goes (or just after it) and hide the standard Searchbox through properties.
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