[BC Idea]: Mark "Post Code" as "OptimizeForTextSearch"
Nobody has claimed this yet.
- Dominant language
- AL
- Stars
- 683
- Forks
- 459
- Avg merge
- 3d 26m
- Merged PRs (30d)
- 633
Description
BC Idea Link
There I no idea for this yet.
Description
We would like to use the new optimized text search functionality in Business Central Function Management.
After enabling optimized text search, users expect to search Customer and Vendor lists by commonly used address-related terms, including the Post Code field. However, the Post Code field on both Customers and Vendors does not appear to be marked with OptimizeForTextSearch, so it is not included in the optimized search experience.
This means users cannot reliably find customers or vendors by post code when using the optimized search, even though post code is a relevant and frequently used search term in these lists.
Expected Behavior:
The Post Code field should be included in optimized text search for the relevant Customer and Vendor tables/pages, so users can search by post code when optimized text search is enabled.
Actual Behavior:
The Post Code field is not included in optimized text search for Customer and Vendor lists, so searches by post code do not return the expected records.
I will provide the implementation for this BC Idea
- I will provide the implementation for this BC Idea
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Customer and Vendor tables or pages and inspect how the Post Code field is configured for optimized text search. Mark the relevant Post Code fields for inclusion, then verify that optimized searches on Customer and Vendor lists can find records by post code.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100