Applies to Product - Dynamics 365 Business Central
What’s happening?
Customers are experiencing issues with the legacy search functionality in Dynamics 365 Business Central, specifically regarding which special characters cannot be detected during searches.
Customers are experiencing issues with the legacy search functionality in Dynamics 365 Business Central, specifically regarding which special characters cannot be detected during searches.
Reason:
This arises because certain special characters, such as "@" and "*", are used as filter conditions in the legacy search functionality. When these characters are included in the target value, they cannot be recognized by the search system.
This arises because certain special characters, such as "@" and "*", are used as filter conditions in the legacy search functionality. When these characters are included in the target value, they cannot be recognized by the search system.
Resolution:
To resolve this, the following steps can be taken:
- When using legacy search, avoid using the "@" symbol as it is treated as a filter condition. For example, searching for "@~1~9" will yield no results, while searching for "~1~9" will return the correct item.
- Similarly, other characters like "*" and "‘" also function as filter conditions and should be avoided in the search queries.
- For standard fields, consider using alternative identifiers such as "Shelf No." instead of custom fields like "Part No.".
- For further reference, consult the documentation on fine-tuning search criteria in legacy search: Microsoft Documentation.
To resolve this, the following steps can be taken:
- When using legacy search, avoid using the "@" symbol as it is treated as a filter condition. For example, searching for "@~1~9" will yield no results, while searching for "~1~9" will return the correct item.
- Similarly, other characters like "*" and "‘" also function as filter conditions and should be avoided in the search queries.
- For standard fields, consider using alternative identifiers such as "Shelf No." instead of custom fields like "Part No.".
- For further reference, consult the documentation on fine-tuning search criteria in legacy search: Microsoft Documentation.