20
Implementing the $search operator in OData will allow a service consumer to specify a search string that can be found in several different fields.
Obviously there would be a performance impact as Business Central service doesn't natively support or queries on different fields, which is likely why the OData OR operator is also not allowed.
I can see this working similarly to DataCaptionFields, where an API Page/Query would have a list of fields specified as being used by the $search operator.
Obviously there would be a performance impact as Business Central service doesn't natively support or queries on different fields, which is likely why the OData OR operator is also not allowed.
I can see this working similarly to DataCaptionFields, where an API Page/Query would have a list of fields specified as being used by the $search operator.
STATUS DETAILS
Needs Votes
Comments
The Business Central web client does already support cross column search using the search field on a list page. In AL-code a developer can user filtergroup -1 to create a SQL query with OR-operators. So I would suspect that implementing the OR-operator over distinct fields would not necessarily be problematic for performance.Having the option to either use OR over distinct fields or use the $search-operator as a means to search for a value over all fields would be beneficial to our product as well.
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