Getting error [HTTP]:500 - [CorrelationId]:572926a0-d0ba-3000-a093-33556b83e8aa [Version]:16.0.0.22216 when searching with two digits seperated by "." e.g. 1.7

[Namrata99sah]

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

Windows

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

• browser version
• SPFx version
• Node.js version
• etc

Describe the bug / error

Search with any 2 digit number separated with decimal, e.g. 1.7, 3.5 the Result is throwing error.

Getting error [HTTP]:500 - [CorrelationId]:572926a0-d0ba-3000-a093-33556b83e8aa [Version]:16.0.0.22216

Observations -

1. Changing the Result Template to "ItemsMatchingTag" is resolving the error from "LocalSharePointResults".
2. Search with quoted text "1.7", "3.5" is returning correct results.
3. The same template is working in other site collection with same settings. For the errored Site "&scope=site" is getting appended in the URL.
4. Searching with 100.1 or three digit is working fine.
5. Disabling the Query Rules is resolving the issue.
   Below is the Network Trace:
   {"request":{"__metadata":{"type":"Microsoft.Office.Server.Search.REST.SearchRequest"},"ClientType":"PnPModernSearch","Properties":{"results":[{"Name":"EnableDynamicGroups","Value":{"BoolVal":true,"QueryPropertyValueTypeIndex":3}},{"Name":"EnableMultiGeoSearch","Value":{"BoolVal":true,"QueryPropertyValueTypeIndex":3}},{"Name":"ClientFunction","Value":{"StrVal":"PnPSearchWebPart","QueryPropertyValueTypeIndex":1}},{"Name":"ListId","Value":{"StrVal":"e956a8c2-c00c-4fec-a3a4-72c2d1f739b3","QueryPropertyValueTypeIndex":1}},{"Name":"ListItemId","Value":{"StrVal":"2573","QueryPropertyValueTypeIndex":1}}]},"Querytext":"1.2","EnableQueryRules":true,"QueryTemplate":"1.2 Path:{Site} AND IsContainer:"false" AND Archived<>"True" 1.2","SourceId":"8413cd39-2156-4e00-b54d-11efd9abdb89","EnableNicknames":false,"EnablePhonetic":false,"Culture":1033,"TimeZoneId":93,"Refiners":"RefinableString01,RefinableString102,RefinableString105,RefinableString04,RefinableDate00(discretize=manual/2021-03-03T15:37:08.352Z/2021-12-03T15:37:08.352Z/2022-02-03T15:37:08.352Z/2022-02-24T15:37:08.352Z/2022-03-02T15:37:08.352Z/2022-03-03T15:38:08.352Z), LastModifiedTime(discretize=manual/2021-03-03T15:37:08.352Z/2021-12-03T15:37:08.352Z/2022-02-03T15:37:08.352Z/2022-02-24T15:37:08.352Z/2022-03-02T15:37:08.352Z/2022-03-03T15:38:08.352Z),FileType","RefinementFilters":{"results":[]},"RowLimit":10,"StartRow":0,"TrimDuplicates":false,"SortList":{"results":[{"Property":"Created","Direction":0},{"Property":"Size","Direction":1}]},"SelectProperties":{"results":["AuthorOWSUSER","contentclass","ContentType","ContentTypeId","Created","CreatedBy","DefaultEncodingURL","FileType","HitHighlightedSummary","IsContainer","JobTitle","LastModifiedTime","NormListID","NormSiteID","NormUniqueID","owstaxidmetadataalltagsinfo","PageURL","Path","PolicyPageURL","RefinableDate00","RefinableString00","RefinableString01","RefinableString02","RefinableString03","RefinableString04","RefinableString05","RefinableString06","RefinableString07","RefinableString08","RefinableString09","RefinableString10","RefinableString100","RefinableString101","RefinableString102","RefinableString103","RefinableString104","RefinableString105","RelatedGroupId","ServerRedirectedEmbedURL","ServerRedirectedPreviewURL","ServerRedirectedURL","SiteLogo","SiteTitle","SPSiteUrl","Title","UniqueID","UserName","WorkPhone"]},"HitHighlightedProperties":{"results":[]},"ReorderingRules":{"results":[]}}}

Steps to reproduce

Expected behavior

It should return the results without error

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[github-actions]

Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.

If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.

We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.